{"push_id":2466112182,"size":1000,"distinct_size":3871,"ref":"refs/heads/lineage-15.0","head":"08fc2eaca944657f27961958f88d09fd33481cf6","before":"8e10a4d0df34bcd4bbb29b8fdff959e937f1e5fa","commits":[{"sha":"8d203407d42b6a8ead9aab295654eec6fd1cafe7","author":{"name":"Luis de Bethencourt","email":"8f75b4f0fcf50ddef066e07e72bb1ea01e2b9de1@osg.samsung.com"},"message":"staging: iio: accel: fix error check\n\ncommit ef3149eb3ddb7f9125e11c90f8330e371b55cffd upstream.\n\nsca3000_read_ctrl_reg() returns a negative number on failure, check for\nthis instead of zero.\n\nSigned-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>\nCc: <Stable@vger.kernel.org>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/8d203407d42b6a8ead9aab295654eec6fd1cafe7"},{"sha":"d4792c325d8ea7599498e4cd0564d30a6341d4f1","author":{"name":"Linus Walleij","email":"9cd9d802d23c0ed5e224beabf4ae4a5c478746ef@linaro.org"},"message":"iio: accel: kxsd9: fix the usage of spi_w8r8()\n\ncommit 0c1f91b98552da49d9d8eed32b3132a58d2f4598 upstream.\n\nThese two spi_w8r8() calls return a value with is used by the code\nfollowing the error check. The dubious use was caused by a cleanup\npatch.\n\nFixes: d34dbee8ac8e (\"staging:iio:accel:kxsd9 cleanup and conversion to iio_chan_spec.\")\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nCc: <Stable@vger.kernel.org>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/d4792c325d8ea7599498e4cd0564d30a6341d4f1"},{"sha":"32ea719b4a72d3599824de62ae1a412cc536a4c7","author":{"name":"Mark Brown","email":"b51b9a92386687a9ac927cebfa0f978adeb8cea5@kernel.org"},"message":"iio:ad7266: Fix broken regulator error handling\n\ncommit 6b7f4e25f3309f106a5c7ff42c8231494cf285d3 upstream.\n\nAll regulator_get() variants return either a pointer to a regulator or an\nERR_PTR() so testing for NULL makes no sense and may lead to bugs if we\nuse NULL as a valid regulator. Fix this by using IS_ERR() as expected.\n\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: <Stable@vger.kernel.org>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/32ea719b4a72d3599824de62ae1a412cc536a4c7"},{"sha":"4cb4e3314f90011ecf111ad93c3b6b5e248f8d03","author":{"name":"Mark Brown","email":"b51b9a92386687a9ac927cebfa0f978adeb8cea5@kernel.org"},"message":"iio:ad7266: Fix probe deferral for vref\n\ncommit 68b356eb3d9f5e38910fb62e22a78e2a18d544ae upstream.\n\nCurrently the ad7266 driver treats any failure to get vref as though the\nregulator were not present but this means that if probe deferral is\ntriggered the driver will act as though the regulator were not present.\nInstead only use the internal reference if we explicitly got -ENODEV which\nis what is returned for absent regulators.\n\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: <Stable@vger.kernel.org>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/4cb4e3314f90011ecf111ad93c3b6b5e248f8d03"},{"sha":"81fa23b2ef950c26850d81f1abfd90a64302dfb4","author":{"name":"Dmitry Torokhov","email":"6b8646d310837fed93a129ed3c979b90c7f2674f@gmail.com"},"message":"tty/vt/keyboard: fix OOB access in do_compute_shiftstate()\n\ncommit 510cccb5b0c8868a2b302a0ab524da7912da648b upstream.\n\nThe size of individual keymap in drivers/tty/vt/keyboard.c is NR_KEYS,\nwhich is currently 256, whereas number of keys/buttons in input device (and\ntherefor in key_down) is much larger - KEY_CNT - 768, and that can cause\nout-of-bound access when we do\n\n\tsym = U(key_maps[0][k]);\n\nwith large 'k'.\n\nTo fix it we should not attempt iterating beyond smaller of NR_KEYS and\nKEY_CNT.\n\nAlso while at it let's switch to for_each_set_bit() instead of open-coding\nit.\n\nReported-by: Sasha Levin <sasha.levin@oracle.com>\nReviewed-by: Guenter Roeck <linux@roeck-us.net>\nCc: stable@vger.kernel.org\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/81fa23b2ef950c26850d81f1abfd90a64302dfb4"},{"sha":"610c23b83537d30f7346357a3158693422e18b08","author":{"name":"Takashi Iwai","email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de"},"message":"ALSA: dummy: Fix a use-after-free at closing\n\ncommit d5dbbe6569481bf12dcbe3e12cff72c5f78d272c upstream.\n\nsyzkaller fuzzer spotted a potential use-after-free case in snd-dummy\ndriver when hrtimer is used as backend:\n> ==================================================================\n> BUG: KASAN: use-after-free in rb_erase+0x1b17/0x2010 at addr ffff88005e5b6f68\n>  Read of size 8 by task syz-executor/8984\n> =============================================================================\n> BUG kmalloc-192 (Not tainted): kasan: bad access detected\n> -----------------------------------------------------------------------------\n>\n> Disabling lock debugging due to kernel taint\n> INFO: Allocated in 0xbbbbbbbbbbbbbbbb age=18446705582212484632\n> ....\n> [<      none      >] dummy_hrtimer_create+0x49/0x1a0 sound/drivers/dummy.c:464\n> ....\n> INFO: Freed in 0xfffd8e09 age=18446705496313138713 cpu=2164287125 pid=-1\n> [<      none      >] dummy_hrtimer_free+0x68/0x80 sound/drivers/dummy.c:481\n> ....\n> Call Trace:\n>  [<ffffffff8179e59e>] __asan_report_load8_noabort+0x3e/0x40 mm/kasan/report.c:333\n>  [<     inline     >] rb_set_parent include/linux/rbtree_augmented.h:111\n>  [<     inline     >] __rb_erase_augmented include/linux/rbtree_augmented.h:218\n>  [<ffffffff82ca5787>] rb_erase+0x1b17/0x2010 lib/rbtree.c:427\n>  [<ffffffff82cb02e8>] timerqueue_del+0x78/0x170 lib/timerqueue.c:86\n>  [<ffffffff814d0c80>] __remove_hrtimer+0x90/0x220 kernel/time/hrtimer.c:903\n>  [<     inline     >] remove_hrtimer kernel/time/hrtimer.c:945\n>  [<ffffffff814d23da>] hrtimer_try_to_cancel+0x22a/0x570 kernel/time/hrtimer.c:1046\n>  [<ffffffff814d2742>] hrtimer_cancel+0x22/0x40 kernel/time/hrtimer.c:1066\n>  [<ffffffff85420531>] dummy_hrtimer_stop+0x91/0xb0 sound/drivers/dummy.c:417\n>  [<ffffffff854228bf>] dummy_pcm_trigger+0x17f/0x1e0 sound/drivers/dummy.c:507\n>  [<ffffffff85392170>] snd_pcm_do_stop+0x160/0x1b0 sound/core/pcm_native.c:1106\n>  [<ffffffff85391b26>] snd_pcm_action_single+0x76/0x120 sound/core/pcm_native.c:956\n>  [<ffffffff85391e01>] snd_pcm_action+0x231/0x290 sound/core/pcm_native.c:974\n>  [<     inline     >] snd_pcm_stop sound/core/pcm_native.c:1139\n>  [<ffffffff8539754d>] snd_pcm_drop+0x12d/0x1d0 sound/core/pcm_native.c:1784\n>  [<ffffffff8539d3be>] snd_pcm_common_ioctl1+0xfae/0x2150 sound/core/pcm_native.c:2805\n>  [<ffffffff8539ee91>] snd_pcm_capture_ioctl1+0x2a1/0x5e0 sound/core/pcm_native.c:2976\n>  [<ffffffff8539f2ec>] snd_pcm_kernel_ioctl+0x11c/0x160 sound/core/pcm_native.c:3020\n>  [<ffffffff853d9a44>] snd_pcm_oss_sync+0x3a4/0xa30 sound/core/oss/pcm_oss.c:1693\n>  [<ffffffff853da27d>] snd_pcm_oss_release+0x1ad/0x280 sound/core/oss/pcm_oss.c:2483\n>  .....\n\nA workaround is to call hrtimer_cancel() in dummy_hrtimer_sync() which\nis called certainly before other blocking ops.\n\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nTested-by: Dmitry Vyukov <dvyukov@google.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/610c23b83537d30f7346357a3158693422e18b08"},{"sha":"b535fbf80de869a9f3138462ea8e06a7c00d1888","author":{"name":"Takashi Iwai","email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de"},"message":"ALSA: au88x0: Fix calculation in vortex_wtdma_bufshift()\n\ncommit 62db7152c924e4c060e42b34a69cd39658e8a0dc upstream.\n\nvortex_wtdma_bufshift() function does calculate the page index\nwrongly, first masking then shift, which always results in zero.\nThe proper computation is to first shift, then mask.\n\nReported-by: Dan Carpenter <dan.carpenter@oracle.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/b535fbf80de869a9f3138462ea8e06a7c00d1888"},{"sha":"1ee21303558d39b846f4bff90a54f517da15141a","author":{"name":"Wei Fang","email":"e9083e8823ccf4d1e7311b2b8bf95b8e9dfa1102@huawei.com"},"message":"scsi: fix race between simultaneous decrements of ->host_failed\n\ncommit 72d8c36ec364c82bf1bf0c64dfa1041cfaf139f7 upstream.\n\nsas_ata_strategy_handler() adds the works of the ata error handler to\nsystem_unbound_wq. This workqueue asynchronously runs work items, so the\nata error handler will be performed concurrently on different CPUs. In\nthis case, ->host_failed will be decreased simultaneously in\nscsi_eh_finish_cmd() on different CPUs, and become abnormal.\n\nIt will lead to permanently inequality between ->host_failed and\n->host_busy, and scsi error handler thread won't start running. IO\nerrors after that won't be handled.\n\nSince all scmds must have been handled in the strategy handler, just\nremove the decrement in scsi_eh_finish_cmd() and zero ->host_busy after\nthe strategy handler to fix this race.\n\nFixes: 50824d6c5657 (\"[SCSI] libsas: async ata-eh\")\nCc: stable@vger.kernel.org\nSigned-off-by: Wei Fang <fangwei1@huawei.com>\nReviewed-by: James Bottomley <jejb@linux.vnet.ibm.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/1ee21303558d39b846f4bff90a54f517da15141a"},{"sha":"8c277bc04da28271e258869236d473d67d3762f0","author":{"name":"Christoph Hellwig","email":"923f7720577207a44b32e59bbfbea59d27f1ae8e@lst.de"},"message":"scsi: remove scsi_end_request\n\ncommit bc85dc500f9df9b2eec15077e5046672c46adeaa upstream.\n\nBy folding scsi_end_request into its only caller we can significantly clean\nup the completion logic.  We can use simple goto labels now to only have\na single place to finish or requeue command there instead of the previous\nconvoluted logic.\n\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nReviewed-by: Nicholas Bellinger <nab@linux-iscsi.org>\nReviewed-by: Mike Christie <michaelc@cs.wisc.edu>\nReviewed-by: Hannes Reinecke <hare@suse.de>\n[jwang: backport to 3.12]\nSigned-off-by: Jack Wang <jinpu.wang@profitbricks.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/8c277bc04da28271e258869236d473d67d3762f0"},{"sha":"c1c2ec76cb409ac7e7ab4500b3391bca0e36ca16","author":{"name":"Steve French","email":"51565b4e5841e493fd669866e11ea3c7c0d781cc@gmail.com"},"message":"Fix reconnect to not defer smb3 session reconnect long after socket reconnect\n\ncommit 4fcd1813e6404dd4420c7d12fb483f9320f0bf93 upstream.\n\nAzure server blocks clients that open a socket and don't do anything on it.\nIn our reconnect scenarios, we can reconnect the tcp session and\ndetect the socket is available but we defer the negprot and SMB3 session\nsetup and tree connect reconnection until the next i/o is requested, but\nthis looks suspicous to some servers who expect SMB3 negprog and session\nsetup soon after a socket is created.\n\nIn the echo thread, reconnect SMB3 sessions and tree connections\nthat are disconnected.  A later patch will replay persistent (and\nresilient) handle opens.\n\nSigned-off-by: Steve French <steve.french@primarydata.com>\nAcked-by: Pavel Shilovsky <pshilovsky@samba.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/c1c2ec76cb409ac7e7ab4500b3391bca0e36ca16"},{"sha":"e2f3f28316f472145568a9cdc712910bccb60619","author":{"name":"Jan Beulich","email":"051346888327db48cce19d2cfd0e1c700bb7cf16@suse.com"},"message":"xen/acpi: allow xen-acpi-processor driver to load on Xen 4.7\n\ncommit 6f2d9d99213514360034c6d52d2c3919290b3504 upstream.\n\nAs of Xen 4.7 PV CPUID doesn't expose either of CPUID[1].ECX[7] and\nCPUID[0x80000007].EDX[7] anymore, causing the driver to fail to load on\nboth Intel and AMD systems. Doing any kind of hardware capability\nchecks in the driver as a prerequisite was wrong anyway: With the\nhypervisor being in charge, all such checking should be done by it. If\nACPI data gets uploaded despite some missing capability, the hypervisor\nis free to ignore part or all of that data.\n\nDitch the entire check_prereq() function, and do the only valid check\n(xen_initial_domain()) in the caller in its place.\n\nSigned-off-by: Jan Beulich <jbeulich@suse.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: David Vrabel <david.vrabel@citrix.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/e2f3f28316f472145568a9cdc712910bccb60619"},{"sha":"314efc997bcd42181dd2f9586dd1bb0209d9e39c","author":{"name":"Jan Willeke","email":"28d44b5e2d4d60984251930f27f859e3893862be@de.ibm.com"},"message":"s390/seccomp: fix error return for filtered system calls\n\ncommit dc295880c6752076f8b94ba3885d0bfff09e3e82 upstream.\n\nThe syscall_set_return_value function of s390 negates the error argument\nbefore storing the value to the return register gpr2. This is incorrect,\nthe seccomp code already passes the negative error value.\nStore the unmodified error value to gpr2.\n\nSigned-off-by: Jan Willeke <willeke@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/314efc997bcd42181dd2f9586dd1bb0209d9e39c"},{"sha":"ff14ba38416845f82b6cba07171ed95943e28fa1","author":{"name":"Torsten Hilbrich","email":"d3e0ad69836cfcb7d3dc03fa1137c1f4f96a3ff0@secunet.com"},"message":"fs/nilfs2: fix potential underflow in call to crc32_le\n\ncommit 63d2f95d63396059200c391ca87161897b99e74a upstream.\n\nThe value `bytes' comes from the filesystem which is about to be\nmounted.  We cannot trust that the value is always in the range we\nexpect it to be.\n\nCheck its value before using it to calculate the length for the crc32_le\ncall.  It value must be larger (or equal) sumoff + 4.\n\nThis fixes a kernel bug when accidentially mounting an image file which\nhad the nilfs2 magic value 0x3434 at the right offset 0x406 by chance.\nThe bytes 0x01 0x00 were stored at 0x408 and were interpreted as a\ns_bytes value of 1.  This caused an underflow when substracting sumoff +\n4 (20) in the call to crc32_le.\n\n  BUG: unable to handle kernel paging request at ffff88021e600000\n  IP:  crc32_le+0x36/0x100\n  ...\n  Call Trace:\n    nilfs_valid_sb.part.5+0x52/0x60 [nilfs2]\n    nilfs_load_super_block+0x142/0x300 [nilfs2]\n    init_nilfs+0x60/0x390 [nilfs2]\n    nilfs_mount+0x302/0x520 [nilfs2]\n    mount_fs+0x38/0x160\n    vfs_kern_mount+0x67/0x110\n    do_mount+0x269/0xe00\n    SyS_mount+0x9f/0x100\n    entry_SYSCALL_64_fastpath+0x16/0x71\n\nLink: http://lkml.kernel.org/r/1466778587-5184-2-git-send-email-konishi.ryusuke@lab.ntt.co.jp\nSigned-off-by: Torsten Hilbrich <torsten.hilbrich@secunet.com>\nTested-by: Torsten Hilbrich <torsten.hilbrich@secunet.com>\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/ff14ba38416845f82b6cba07171ed95943e28fa1"},{"sha":"d97a581ccf46db5d86f751309f4a82862ab6bcdd","author":{"name":"Alexey Brodkin","email":"df74735e5e8e4da139876d19d7450f461d604b9f@synopsys.com"},"message":"arc: unwind: warn only once if DW2_UNWIND is disabled\n\ncommit 9bd54517ee86cb164c734f72ea95aeba4804f10b upstream.\n\nIf CONFIG_ARC_DW2_UNWIND is disabled every time arc_unwind_core()\ngets called following message gets printed in debug console:\n----------------->8---------------\nCONFIG_ARC_DW2_UNWIND needs to be enabled\n----------------->8---------------\n\nThat message makes sense if user indeed wants to see a backtrace or\nget nice function call-graphs in perf but what if user disabled\nunwinder for the purpose? Why pollute his debug console?\n\nSo instead we'll warn user about possibly missing feature once and\nlet him decide if that was what he or she really wanted.\n\nSigned-off-by: Alexey Brodkin <abrodkin@synopsys.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/d97a581ccf46db5d86f751309f4a82862ab6bcdd"},{"sha":"c6b5c33a1abc2cfeb1179a5b35523ff370e0b596","author":{"name":"Andrey Grodzovsky","email":"4264cc854950dcb74d80096874d050fcccce21eb@gmail.com"},"message":"xen/pciback: Fix conf_space read/write overlap check.\n\ncommit 02ef871ecac290919ea0c783d05da7eedeffc10e upstream.\n\nCurrent overlap check is evaluating to false a case where a filter\nfield is fully contained (proper subset) of a r/w request.  This\nchange applies classical overlap check instead to include all the\nscenarios.\n\nMore specifically, for (Hilscher GmbH CIFX 50E-DP(M/S)) device driver\nthe logic is such that the entire confspace is read and written in 4\nbyte chunks. In this case as an example, CACHE_LINE_SIZE,\nLATENCY_TIMER and PCI_BIST are arriving together in one call to\nxen_pcibk_config_write() with offset == 0xc and size == 4.  With the\nexsisting overlap check the LATENCY_TIMER field (offset == 0xd, length\n== 1) is fully contained in the write request and hence is excluded\nfrom write, which is incorrect.\n\nSigned-off-by: Andrey Grodzovsky <andrey2805@gmail.com>\nReviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>\nReviewed-by: Jan Beulich <JBeulich@suse.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: David Vrabel <david.vrabel@citrix.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/c6b5c33a1abc2cfeb1179a5b35523ff370e0b596"},{"sha":"8044dddec9cba4aa272abff9a29e9c7c0dbf14cc","author":{"name":"Jeff Mahoney","email":"5459ed423adecc5a7fe2249dd619058acc25c497@suse.com"},"message":"Revert \"ecryptfs: forbid opening files without mmap handler\"\n\ncommit 78c4e172412de5d0456dc00d2b34050aa0b683b5 upstream.\n\nThis reverts commit 2f36db71009304b3f0b95afacd8eba1f9f046b87.\n\nIt fixed a local root exploit but also introduced a dependency on\nthe lower file system implementing an mmap operation just to open a file,\nwhich is a bit of a heavy hammer.  The right fix is to have mmap depend\non the existence of the mmap handler instead.\n\nSigned-off-by: Jeff Mahoney <jeffm@suse.com>\nSigned-off-by: Tyler Hicks <tyhicks@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/8044dddec9cba4aa272abff9a29e9c7c0dbf14cc"},{"sha":"1cc3a46813156fbdc9e116525139f6373d0c2d4d","author":{"name":"Vineet Gupta","email":"af669d95a4c0de051445d4cafdbb2c5c4a2838be@synopsys.com"},"message":"ARC: use ASL assembler mnemonic\n\ncommit a6416f57ce57fb390b6ee30b12c01c29032a26af upstream.\n\nARCompact and ARCv2 only have ASL, while binutils used to support LSL as\na alias mnemonic.\n\nNewer binutils (upstream) don't want to do that so replace it.\n\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/1cc3a46813156fbdc9e116525139f6373d0c2d4d"},{"sha":"acc7b2a300d8c3bf7b8c8cb39a9b0513b6f066da","author":{"name":"Ursula Braun","email":"987b0c426d2723ff49ca4d5570ccdff86d96266c@linux.vnet.ibm.com"},"message":"qeth: delete napi struct when removing a qeth device\n\ncommit 7831b4ff0d926e0deeaabef9db8800ed069a2757 upstream.\n\nA qeth_card contains a napi_struct linked to the net_device during\ndevice probing. This struct must be deleted when removing the qeth\ndevice, otherwise Panic on oops can occur when qeth devices are\nrepeatedly removed and added.\n\nFixes: a1c3ed4c9ca (\"qeth: NAPI support for l2 and l3 discipline\")\nCc: stable@vger.kernel.org # v2.6.37+\nSigned-off-by: Ursula Braun <ubraun@linux.vnet.ibm.com>\nTested-by: Alexander Klein <ALKL@de.ibm.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/acc7b2a300d8c3bf7b8c8cb39a9b0513b6f066da"},{"sha":"894e1c9c0ce1b5401fcd8d132d08ac5fcf9959bf","author":{"name":"Taras Kondratiuk","email":"52954a24167d5a9980fa724814d6c71c4c0faf06@cisco.com"},"message":"mmc: block: fix packed command header endianness\n\ncommit f68381a70bb2b26c31b13fdaf67c778f92fd32b4 upstream.\n\nThe code that fills packed command header assumes that CPU runs in\nlittle-endian mode. Hence the header is malformed in big-endian mode\nand causes MMC data transfer errors:\n\n[  563.200828] mmcblk0: error -110 transferring data, sector 2048, nr 8, cmd response 0x900, card status 0xc40\n[  563.219647] mmcblk0: packed cmd failed, nr 2, sectors 16, failure index: -1\n\nConvert header data to LE.\n\nSigned-off-by: Taras Kondratiuk <takondra@cisco.com>\nFixes: ce39f9d17c14 (\"mmc: support packed write command for eMMC4.5 devices\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/894e1c9c0ce1b5401fcd8d132d08ac5fcf9959bf"},{"sha":"02a23317eb862509cbb13d617cd96f658ce7ebea","author":{"name":"Wolfgang Grandegger","email":"5aa1976eca1fee4e35c7b71ec8e8a0ebad9da3d1@grandegger.com"},"message":"can: at91_can: RX queue could get stuck at high bus load\n\ncommit 43200a4480cbbe660309621817f54cbb93907108 upstream.\n\nAt high bus load it could happen that \"at91_poll()\" enters with all RX\nmessage boxes filled up. If then at the end the \"quota\" is exceeded as\nwell, \"rx_next\" will not be reset to the first RX mailbox and hence the\ninterrupts remain disabled.\n\nSigned-off-by: Wolfgang Grandegger <wg@grandegger.com>\nTested-by: Amr Bekhit <amrbekhit@gmail.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Marc Kleine-Budde <mkl@pengutronix.de>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/deepakgangwar/android_kernel_motorola_msm8952/commits/02a23317eb862509cbb13d617cd96f658ce7ebea"}]}
{"actor":{"display_login":"deepakgangwar"}}