{"push_id":1110609637,"size":252,"distinct_size":6,"ref":"refs/heads/github-kvalo/master","head":"6823a630bd373e2cf40419cea13d6cb4286c216c","before":"d11f592e0e456178419b1883b0014b379c4eb60c","commits":[{"sha":"dcf5341f0150bc4c5bf37786e1198d2ff8fc2c38","author":{"email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com","name":"Hans de Goede"},"message":"ARM: dts: sun8i-q8-common: Do not set constraints on dc1sw regulator\n\ndc1sw is an on/off only regulator and as such it cannot have constraints.\n\nThis is a limitation of the kernel regulator implementation which resolves\nsupplies on the first regulator_get(), which is done after applying\nconstraints, and applying the constrains will fail because it calls\n_regulator_get_voltage() and _regulator_do_set_voltage() both of which\nwill fail on a switch regulator when there is no supply (yet).\n\nThis causes registering of all axp22x regulators to fail with the\nfollowing errors:\n\n[    1.395249] vcc-lcd: failed to get the current voltage(-22)\n[    1.405131] axp20x-regulator axp20x-regulator: Failed to register dc1sw\n[    1.412436] axp20x-regulator: probe of axp20x-regulator failed with error -22\n\nThis commit removes the constrains on dc1sw / vcc-lcd fixing this problem\nnote that dcdc1 itself is contrained to the exact same values, so this\ndoes not change anything.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/dcf5341f0150bc4c5bf37786e1198d2ff8fc2c38"},{"sha":"d0c31e02005764dae0aab130a57e9794d06b824d","author":{"email":"fc83b762ab7666c2f8f765f26b2c5088d16d49d7@oracle.com","name":"Babu Moger"},"message":"sparc/PCI: Fix for panic while enabling SR-IOV\n\nWe noticed this panic while enabling SR-IOV in sparc.\n\nmlx4_core: Mellanox ConnectX core driver v2.2-1 (Jan  1 2015)\nmlx4_core: Initializing 0007:01:00.0\nmlx4_core 0007:01:00.0: Enabling SR-IOV with 5 VFs\nmlx4_core: Initializing 0007:01:00.1\nUnable to handle kernel NULL pointer dereference\ninsmod(10010): Oops [#1]\nCPU: 391 PID: 10010 Comm: insmod Not tainted\n\t\t4.1.12-32.el6uek.kdump2.sparc64 #1\nTPC: <dma_supported+0x20/0x80>\nI7: <__mlx4_init_one+0x324/0x500 [mlx4_core]>\nCall Trace:\n [00000000104c5ea4] __mlx4_init_one+0x324/0x500 [mlx4_core]\n [00000000104c613c] mlx4_init_one+0xbc/0x120 [mlx4_core]\n [0000000000725f14] local_pci_probe+0x34/0xa0\n [0000000000726028] pci_call_probe+0xa8/0xe0\n [0000000000726310] pci_device_probe+0x50/0x80\n [000000000079f700] really_probe+0x140/0x420\n [000000000079fa24] driver_probe_device+0x44/0xa0\n [000000000079fb5c] __device_attach+0x3c/0x60\n [000000000079d85c] bus_for_each_drv+0x5c/0xa0\n [000000000079f588] device_attach+0x88/0xc0\n [000000000071acd0] pci_bus_add_device+0x30/0x80\n [0000000000736090] virtfn_add.clone.1+0x210/0x360\n [00000000007364a4] sriov_enable+0x2c4/0x520\n [000000000073672c] pci_enable_sriov+0x2c/0x40\n [00000000104c2d58] mlx4_enable_sriov+0xf8/0x180 [mlx4_core]\n [00000000104c49ac] mlx4_load_one+0x42c/0xd40 [mlx4_core]\nDisabling lock debugging due to kernel taint\nCaller[00000000104c5ea4]: __mlx4_init_one+0x324/0x500 [mlx4_core]\nCaller[00000000104c613c]: mlx4_init_one+0xbc/0x120 [mlx4_core]\nCaller[0000000000725f14]: local_pci_probe+0x34/0xa0\nCaller[0000000000726028]: pci_call_probe+0xa8/0xe0\nCaller[0000000000726310]: pci_device_probe+0x50/0x80\nCaller[000000000079f700]: really_probe+0x140/0x420\nCaller[000000000079fa24]: driver_probe_device+0x44/0xa0\nCaller[000000000079fb5c]: __device_attach+0x3c/0x60\nCaller[000000000079d85c]: bus_for_each_drv+0x5c/0xa0\nCaller[000000000079f588]: device_attach+0x88/0xc0\nCaller[000000000071acd0]: pci_bus_add_device+0x30/0x80\nCaller[0000000000736090]: virtfn_add.clone.1+0x210/0x360\nCaller[00000000007364a4]: sriov_enable+0x2c4/0x520\nCaller[000000000073672c]: pci_enable_sriov+0x2c/0x40\nCaller[00000000104c2d58]: mlx4_enable_sriov+0xf8/0x180 [mlx4_core]\nCaller[00000000104c49ac]: mlx4_load_one+0x42c/0xd40 [mlx4_core]\nCaller[00000000104c5f90]: __mlx4_init_one+0x410/0x500 [mlx4_core]\nCaller[00000000104c613c]: mlx4_init_one+0xbc/0x120 [mlx4_core]\nCaller[0000000000725f14]: local_pci_probe+0x34/0xa0\nCaller[0000000000726028]: pci_call_probe+0xa8/0xe0\nCaller[0000000000726310]: pci_device_probe+0x50/0x80\nCaller[000000000079f700]: really_probe+0x140/0x420\nCaller[000000000079fa24]: driver_probe_device+0x44/0xa0\nCaller[000000000079fb08]: __driver_attach+0x88/0xa0\nCaller[000000000079d90c]: bus_for_each_dev+0x6c/0xa0\nCaller[000000000079f29c]: driver_attach+0x1c/0x40\nCaller[000000000079e35c]: bus_add_driver+0x17c/0x220\nCaller[00000000007a02d4]: driver_register+0x74/0x120\nCaller[00000000007263fc]: __pci_register_driver+0x3c/0x60\nCaller[00000000104f62bc]: mlx4_init+0x60/0xcc [mlx4_core]\nKernel panic - not syncing: Fatal exception\nPress Stop-A (L1-A) to return to the boot prom\n---[ end Kernel panic - not syncing: Fatal exception\n\nDetails:\nHere is the call sequence\nvirtfn_add->__mlx4_init_one->dma_set_mask->dma_supported\n\nThe panic happened at line 760(file arch/sparc/kernel/iommu.c)\n\n758 int dma_supported(struct device *dev, u64 device_mask)\n759 {\n760         struct iommu *iommu = dev->archdata.iommu;\n761         u64 dma_addr_mask = iommu->dma_addr_mask;\n762\n763         if (device_mask >= (1UL << 32UL))\n764                 return 0;\n765\n766         if ((device_mask & dma_addr_mask) == dma_addr_mask)\n767                 return 1;\n768\n769 #ifdef CONFIG_PCI\n770         if (dev_is_pci(dev))\n771\t\treturn pci64_dma_supported(to_pci_dev(dev), device_mask);\n772 #endif\n773\n774         return 0;\n775 }\n776 EXPORT_SYMBOL(dma_supported);\n\nSame panic happened with Intel ixgbe driver also.\n\nSR-IOV code looks for arch specific data while enabling\nVFs. When VF device is added, driver probe function makes set\nof calls to initialize the pci device. Because the VF device is\nadded different way than the normal PF device(which happens via\nof_create_pci_dev for sparc), some of the arch specific initialization\ndoes not happen for VF device.  That causes panic when archdata is\naccessed.\n\nTo fix this, I have used already defined weak function\npcibios_setup_device to copy archdata from PF to VF.\nAlso verified the fix.\n\nSigned-off-by: Babu Moger <babu.moger@oracle.com>\nSigned-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>\nReviewed-by: Ethan Zhao <ethan.zhao@oracle.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/d0c31e02005764dae0aab130a57e9794d06b824d"},{"sha":"5ec712934ce1ff6e33bf3878034a91ca9bd600c9","author":{"email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@davemloft.net","name":"David S. Miller"},"message":"sparc: Write up preadv2/pwritev2 syscalls.\n\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/5ec712934ce1ff6e33bf3878034a91ca9bd600c9"},{"sha":"2fd0f46cb1b82587c7ae4a616d69057fb9bd0af7","author":{"email":"e9a3fcd7365f8e6a430ada3b68b984cb4aaf0c3e@linaro.org","name":"Srinivas Kandagatla"},"message":"libahci: save port map for forced port map\n\nIn usecases where force_port_map is used saved_port_map is never set,\nresulting in not programming the PORTS_IMPL register as part of initial\nconfig. This patch fixes this by setting it to port_map even in case\nwhere force_port_map is used, making it more inline with other parts of\nthe code.\n\nFixes: 566d1827df2e (\"libata: disable forced PORTS_IMPL for >= AHCI 1.3\")\nCc: stable@vger.kernel.org # v4.5+\nSigned-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>\nAcked-by: Tejun Heo <tj@kernel.org>\nReviewed-by: Andy Gross <andy.gross@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/2fd0f46cb1b82587c7ae4a616d69057fb9bd0af7"},{"sha":"17dcc37e3e847bc0e67a5b1ec52471fcc6c18682","author":{"email":"e9a3fcd7365f8e6a430ada3b68b984cb4aaf0c3e@linaro.org","name":"Srinivas Kandagatla"},"message":"ata: ahci-platform: Add ports-implemented DT bindings.\n\nOn some SOCs PORTS_IMPL register value is never programmed by the\nfirmware and left at zero value. Which means that no sata ports are\navailable for software. AHCI driver used to cope up with this by\nfabricating the port_map if the PORTS_IMPL register is read zero,\nbut recent patch broke this workaround as zero value was valid for\nNVMe disks.\n\nThis patch adds ports-implemented DT bindings as workaround for this issue\nin a way that DT can can override the PORTS_IMPL register in cases where\nthe firmware did not program it already.\n\nFixes: 566d1827df2e (\"libata: disable forced PORTS_IMPL for >= AHCI 1.3\")\nCc: stable@vger.kernel.org # v4.5+\nSigned-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>\nAcked-by: Tejun Heo <tj@kernel.org>\nReviewed-by: Andy Gross <andy.gross@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/17dcc37e3e847bc0e67a5b1ec52471fcc6c18682"},{"sha":"bb4add2ce991e4ec891b5a0287fd1ab77b631979","author":{"email":"e9a3fcd7365f8e6a430ada3b68b984cb4aaf0c3e@linaro.org","name":"Srinivas Kandagatla"},"message":"ARM: dts: apq8064: add ahci ports-implemented mask\n\nThis patch adds new ports-implemented mask, which is required to get\nachi working on the mainline. Without this patch value read from\nPORTS_IMPL register which is zero would not enable any ports for\nsoftware to use.\n\nFixes: 566d1827df2e (\"libata: disable forced PORTS_IMPL for >= AHCI 1.3\")\nCc: stable@vger.kernel.org # v4.5+\nSigned-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>\nReviewed-by: Andy Gross <andy.gross@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/bb4add2ce991e4ec891b5a0287fd1ab77b631979"},{"sha":"60901df3aed230d4565dca003f11b6a95fbf30d9","author":{"email":"d769abb2ab51a4b3c6d56e5ec4ccdd860b82f07a@citrix.com","name":"Ross Lagerwall"},"message":"xen: Fix page <-> pfn conversion on 32 bit systems\n\nCommit 1084b1988d22dc165c9dbbc2b0e057f9248ac4db (xen: Add Xen specific\npage definition) caused a regression in 4.4.\n\nThe xen functions to convert between pages and pfns fail due to an\noverflow on systems where a physical address may not fit in an\nunsigned long (e.g. x86 32 bit PAE systems). Rework the conversion to\navoid overflow. This should also result in simpler object code.\n\nThis bug manifested itself as disk corruption with Linux 4.4 when\nusing blkfront in a Xen HVM x86 32 bit guest with more than 4 GiB of\nmemory.\n\nSigned-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>\nCc: <stable@vger.kernel.org> # 4.4+\nSigned-off-by: David Vrabel <david.vrabel@citrix.com>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/60901df3aed230d4565dca003f11b6a95fbf30d9"},{"sha":"dfd74a1edfaba5864276a2859190a8d242d18952","author":{"email":"d769abb2ab51a4b3c6d56e5ec4ccdd860b82f07a@citrix.com","name":"Ross Lagerwall"},"message":"xen/balloon: Fix crash when ballooning on x86 32 bit PAE\n\nCommit 55b3da98a40dbb3776f7454daf0d95dde25c33d2 (xen/balloon: find\nnon-conflicting regions to place hotplugged memory) caused a\nregression in 4.4.\n\nWhen ballooning on an x86 32 bit PAE system with close to 64 GiB of\nmemory, the address returned by allocate_resource may be above 64 GiB.\nWhen using CONFIG_SPARSEMEM, this setup is limited to using physical\naddresses < 64 GiB.  When adding memory at this address, it runs off\nthe end of the mem_section array and causes a crash.  Instead, fail\nthe ballooning request.\n\nSigned-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>\nCc: <stable@vger.kernel.org> # 4.4+\nSigned-off-by: David Vrabel <david.vrabel@citrix.com>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/dfd74a1edfaba5864276a2859190a8d242d18952"},{"sha":"42c25013ca95ce79b4ed192188ca843ae48f8c71","author":{"email":"9cd9d802d23c0ed5e224beabf4ae4a5c478746ef@linaro.org","name":"Linus Walleij"},"message":"Revert \"gpio: rcar: Add Runtime PM handling for interrupts\"\n\nThis reverts commit b26a719bdba9aa926ceaadecc66e07623d2b8a53.","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/42c25013ca95ce79b4ed192188ca843ae48f8c71"},{"sha":"ce0e2c60e69e5f87ab4ac10c935d8bd85d4d11f7","author":{"email":"9cd9d802d23c0ed5e224beabf4ae4a5c478746ef@linaro.org","name":"Linus Walleij"},"message":"Revert \"gpio: rcar: Fine-grained Runtime PM support\"\n\nThis reverts commit 65194cb174b873448b208eb6e04ecb72237af76e.","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/ce0e2c60e69e5f87ab4ac10c935d8bd85d4d11f7"},{"sha":"e1123fe975852cc0970b4e53ea65ca917e54c923","author":{"email":"cf6c73a6ee0b37e70e0e9d5446f5db755c00575b@gmail.com","name":"Ping Cheng"},"message":"HID: wacom: Add support for DTK-1651\n\nDTK-1651 is a display pen-only tablet\n\nSigned-off-by: Ping Cheng <pingc@wacom.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/e1123fe975852cc0970b4e53ea65ca917e54c923"},{"sha":"7196c52c9377df0175b510ff5896bda524f7345e","author":{"email":"ba70e185ad5f8bd89713de0ae0734e59d08b9ad3@KARO-electronics.de","name":"Lothar Waßmann"},"message":"clk: imx6q: fix typo in CAN clock definition\n\ncommit ee36027427c7 (\"clk: imx: Add clock support for imx6qp\")\nintroduced a regression due to a subtle typo in the 'can_root' clock\ndefinition. The effect is that trying to configure the bitrate of the\ncan interfaces fails with -EDOM or produces a division by zero error\ndue to the clock_freq of the can serial clock being reported as '0'.\n\nSigned-off-by: Lothar Waßmann <LW@KARO-electronics.de>\nFixes: ee36027427c7 (\"clk: imx: Add clock support for imx6qp\")\nSigned-off-by: Shawn Guo <shawnguo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/7196c52c9377df0175b510ff5896bda524f7345e"},{"sha":"535dac4ab5f42e040e8405b31e309a6b6d4eee57","author":{"email":"6c1ba716601dd19ee463759bfdaf6de1e69b2b21@amd.com","name":"Brijesh Singh"},"message":"ata: add AMD Seattle platform driver\n\nAMD Seattle SATA controller mostly conforms to AHCI interface with some\nspecial register to control SGPIO interface. In the case of an AHCI\ncontroller, the SGPIO feature is ideally implemented using the\n\"Enclosure Management\" register of the AHCI controller, but those\nregisteres are not implemented in the Seattle SoC. Instead SoC\n(Rev B0 onwards) provides a 32-bit SGPIO control register which should\nbe programmed to control the activity, locate and fault LEDs.\n\nThe driver is based on ahci_platform driver.\n\nSigned-off-by: Brijesh Singh <brijesh.singh@amd.com>\nAcked-by: Hans de Goede <hdegoede@redhat.com>\nCC: tj@kernel.org\nCC: linux-ide@vger.kernel.org\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/535dac4ab5f42e040e8405b31e309a6b6d4eee57"},{"sha":"7dedd15dd2527055390b9742c87a02556d3180f4","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"md/raid0: fix uninitialized variable bug\n\nIf this function fails the callers expect that *private_conf is set to\nan ERR_PTR() but that isn't true for the first error path where we can't\nallocate \"conf\".  It leads to some uninitialized variable bugs.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Shaohua Li <shli@fb.com>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/7dedd15dd2527055390b9742c87a02556d3180f4"},{"sha":"2c49477f2a0fdccfe4765326efa5567c5b259aa1","author":{"email":"010521127f513270fe503d86ab8316ac5147f4b7@codeaurora.org","name":"Stephen Boyd"},"message":"Merge tag 'imx-clk-fixes-4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into clk-fixes\n\nThe i.MX clk fixes for 4.6:\n - Fix the typo in CAN clock definition which is introduced by commit\n   ee36027427c7 (\"clk: imx: Add clock support for imx6qp\")\n\n* tag 'imx-clk-fixes-4.6' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux:\n  clk: imx6q: fix typo in CAN clock definition","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/2c49477f2a0fdccfe4765326efa5567c5b259aa1"},{"sha":"07d2390e36ee5b3265e9cc8305f2a106c8721e16","author":{"email":"1a8531307367602b8284517edb33d53d54e5ce8e@samsung.com","name":"Krzysztof Kozlowski"},"message":"iio: ak8975: Fix NULL pointer exception on early interrupt\n\nIn certain probe conditions the interrupt came right after registering\nthe handler causing a NULL pointer exception because of uninitialized\nwaitqueue:\n\n$ udevadm trigger\ni2c-gpio i2c-gpio-1: using pins 143 (SDA) and 144 (SCL)\ni2c-gpio i2c-gpio-3: using pins 53 (SDA) and 52 (SCL)\nUnable to handle kernel NULL pointer dereference at virtual address 00000000\npgd = e8b38000\n[00000000] *pgd=00000000\nInternal error: Oops: 5 [#1] SMP ARM\nModules linked in: snd_soc_i2s(+) i2c_gpio(+) snd_soc_idma snd_soc_s3c_dma snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore ac97_bus spi_s3c64xx pwm_samsung dwc2 exynos_adc phy_exynos_usb2 exynosdrm exynos_rng rng_core rtc_s3c\nCPU: 0 PID: 717 Comm: data-provider-m Not tainted 4.6.0-rc1-next-20160401-00011-g1b8d87473b9e-dirty #101\nHardware name: SAMSUNG EXYNOS (Flattened Device Tree)\n(...)\n(__wake_up_common) from [<c0379624>] (__wake_up+0x38/0x4c)\n(__wake_up) from [<c0a41d30>] (ak8975_irq_handler+0x28/0x30)\n(ak8975_irq_handler) from [<c0386720>] (handle_irq_event_percpu+0x88/0x140)\n(handle_irq_event_percpu) from [<c038681c>] (handle_irq_event+0x44/0x68)\n(handle_irq_event) from [<c0389c40>] (handle_edge_irq+0xf0/0x19c)\n(handle_edge_irq) from [<c0385e04>] (generic_handle_irq+0x24/0x34)\n(generic_handle_irq) from [<c05ee360>] (exynos_eint_gpio_irq+0x50/0x68)\n(exynos_eint_gpio_irq) from [<c0386720>] (handle_irq_event_percpu+0x88/0x140)\n(handle_irq_event_percpu) from [<c038681c>] (handle_irq_event+0x44/0x68)\n(handle_irq_event) from [<c0389a70>] (handle_fasteoi_irq+0xb4/0x194)\n(handle_fasteoi_irq) from [<c0385e04>] (generic_handle_irq+0x24/0x34)\n(generic_handle_irq) from [<c03860b4>] (__handle_domain_irq+0x5c/0xb4)\n(__handle_domain_irq) from [<c0301774>] (gic_handle_irq+0x54/0x94)\n(gic_handle_irq) from [<c030c910>] (__irq_usr+0x50/0x80)\n\nThe bug was reproduced on exynos4412-trats2 (with a max77693 device also\nusing i2c-gpio) after building max77693 as a module.\n\nCc: <stable@vger.kernel.org>\nFixes: 94a6d5cf7caa (\"iio:ak8975 Implement data ready interrupt handling\")\nSigned-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nTested-by: Gregor Boirie <gregor.boirie@parrot.com>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/07d2390e36ee5b3265e9cc8305f2a106c8721e16"},{"sha":"05be8d4101d960bad271d32b4f6096af1ccb1534","author":{"email":"34c6fceca75e456f25e7e99531e2425c6c1de443@g0hl1n.net","name":"Richard Leitner"},"message":"iio: ak8975: fix maybe-uninitialized warning\n\nIf i2c_device_id *id is NULL and acpi_match_device returns NULL too,\nthen chipset may be unitialized when accessing &ak_def_array[chipset] in\nak8975_probe. Therefore initialize chipset to AK_MAX_TYPE, which will\nreturn an error when not changed.\n\nThis patch fixes the following maybe-uninitialized warning:\n\ndrivers/iio/magnetometer/ak8975.c: In function ‘ak8975_probe’:\ndrivers/iio/magnetometer/ak8975.c:788:14: warning: ‘chipset’ may be used\nuninitialized in this function [-Wmaybe-uninitialized]\n  data->def = &ak_def_array[chipset];\n\nSigned-off-by: Richard Leitner <dev@g0hl1n.net>\nCc: <Stable@vger.kernel.org>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/05be8d4101d960bad271d32b4f6096af1ccb1534"},{"sha":"8e6cb470bac6b1e7afa4642a40a71f9bcd066242","author":{"email":"f40600653b33f5282fa4c5daf377dfc444fb4625@denx.de","name":"Marek Vasut"},"message":"iio:adc:at91-sama5d2: Repair crash on module removal\n\nThe driver never calls platform_set_drvdata() , so platform_get_drvdata()\nin .remove returns NULL and thus $indio_dev variable in .remove is NULL.\nThen it's only a matter of dereferencing the indio_dev variable to make\nthe kernel blow as seen below. This patch adds the platform_set_drvdata()\ncall to fix the problem.\n\nroot@armhf:~# rmmod at91-sama5d2_adc\n\nUnable to handle kernel NULL pointer dereference at virtual address 000001d4\npgd = dd57c000\n[000001d4] *pgd=00000000\nInternal error: Oops: 5 [#1] ARM\nModules linked in: at91_sama5d2_adc(-)\nCPU: 0 PID: 1334 Comm: rmmod Not tainted 4.6.0-rc3-next-20160418+ #3\nHardware name: Atmel SAMA5\ntask: dd4fcc40 ti: de910000 task.ti: de910000\nPC is at mutex_lock+0x4/0x24\nLR is at iio_device_unregister+0x14/0x6c\npc : [<c05f4624>]    lr : [<c0471f74>]    psr: a00d0013\n               sp : de911f00  ip : 00000000  fp : be898bd8\nr10: 00000000  r9 : de910000  r8 : c0107724\nr7 : 00000081  r6 : bf001048  r5 : 000001d4  r4 : 00000000\nr3 : bf000000  r2 : 00000000  r1 : 00000004  r0 : 000001d4\nFlags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none\nControl: 10c53c7d  Table: 3d57c059  DAC: 00000051\nProcess rmmod (pid: 1334, stack limit = 0xde910208)\nStack: (0xde911f00 to 0xde912000)\n1f00: bf000000 00000000 df5c7e10 bf000010 bf000000 df5c7e10 df5c7e10 c0351ca8\n1f20: c0351c84 df5c7e10 bf001048 c0350734 bf001048 df5c7e10 df5c7e44 c035087c\n1f40: bf001048 7f62dd4c 00000800 c034fb30 bf0010c0 c0158ee8 de910000 31397461\n1f60: 6d61735f 32643561 6364615f 00000000 de911f90 de910000 de910000 00000000\n1f80: de911fb0 10c53c7d de911f9c c05f33d8 de911fa0 00910000 be898ecb 7f62dd10\n1fa0: 00000000 c0107560 be898ecb 7f62dd10 7f62dd4c 00000800 6f844800 6f844800\n1fc0: be898ecb 7f62dd10 00000000 00000081 00000000 7f62dd10 be898bd8 be898bd8\n1fe0: b6eedab1 be898b6c 7f61056b b6eedab6 000d0030 7f62dd4c 00000000 00000000\n[<c05f4624>] (mutex_lock) from [<c0471f74>] (iio_device_unregister+0x14/0x6c)\n[<c0471f74>] (iio_device_unregister) from [<bf000010>] (at91_adc_remove+0x10/0x3c [at91_sama5d2_adc])\n[<bf000010>] (at91_adc_remove [at91_sama5d2_adc]) from [<c0351ca8>] (platform_drv_remove+0x24/0x3c)\n[<c0351ca8>] (platform_drv_remove) from [<c0350734>] (__device_release_driver+0x84/0x110)\n[<c0350734>] (__device_release_driver) from [<c035087c>] (driver_detach+0x8c/0x90)\n[<c035087c>] (driver_detach) from [<c034fb30>] (bus_remove_driver+0x4c/0xa0)\n[<c034fb30>] (bus_remove_driver) from [<c0158ee8>] (SyS_delete_module+0x110/0x1d0)\n[<c0158ee8>] (SyS_delete_module) from [<c0107560>] (ret_fast_syscall+0x0/0x3c)\nCode: e3520001 1affffd5 eafffff4 f5d0f000 (e1902f9f)\n---[ end trace 86914d7ad3696fca ]---\n\nSigned-off-by: Marek Vasut <marex@denx.de>\nCc: Ludovic Desroches <ludovic.desroches@atmel.com>\nCc: <Stable@vger.kernel.org>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/8e6cb470bac6b1e7afa4642a40a71f9bcd066242"},{"sha":"d4f6e272f2600bc1295d195a52a9e8bb81656bc7","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"firmware: qemu_fw_cfg.c: potential unintialized variable\n\nIt acpi_acquire_global_lock() return AE_NOT_CONFIGURED then \"glk\" isn't\ninitialized, which, if you got very unlucky, could cause a bug.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Michael S. Tsirkin <mst@redhat.com>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/d4f6e272f2600bc1295d195a52a9e8bb81656bc7"},{"sha":"a95f94bc98754bad32cb7f36c867d71f3f2be729","author":{"email":"0691a664b24b6f15b20cd5aee64b72271db08be1@suse.de","name":"Borislav Petkov"},"message":"sparc/defconfigs: Remove CONFIG_IPV6_PRIVACY\n\nOption is long gone, see\n\n  5d9efa7ee99e (\"ipv6: Remove privacy config option.\")\n\nSigned-off-by: Borislav Petkov <bp@suse.de>\nCc: sparclinux@vger.kernel.org\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/a95f94bc98754bad32cb7f36c867d71f3f2be729"}]}