{"push_id":857006120,"size":220,"distinct_size":220,"ref":"refs/heads/cm-13.0","head":"5acecbf618f396c5c7c96948b422ffb05a2e6984","before":"3bfa797134858ddef7b7a0c8a398f0ad52b1b740","commits":[{"sha":"9a6fbaeb68f43f252c204e2ecf87a5d984b35a9d","author":{"email":"9d57ad6bea65ad3984b1761abe00c46e51dcbf41@huawei.com","name":"Weilong Chen"},"message":"ipv6: add check for blackhole or prohibited entry in rt6_redire\n\nThere's a check for ip6_null_entry, but it's not enough if the config\nCONFIG_IPV6_MULTIPLE_TABLES is selected. Blackhole or prohibited entries\nshould also be ignored.\n\nThis path is for kernel before v3.6, as there's a commit b94f1c0\nuse icmpv6_notify() instead of rt6_redirect() and rt6_redirect has\nbeen deleted.\n\nThe oops as follow:\n    [exception RIP: do_raw_write_lock+12]\n    RIP: ffffffff8122c42c  RSP: ffff880666e45820  RFLAGS: 00010282\n    RAX: ffff8801207bffd8  RBX: 0000000000000018  RCX: 0000000000000000\n    RDX: 0000000000000000  RSI: ffff880666e45898  RDI: 0000000000000018\n    RBP: ffff880666e45830   R8: 000000000000001e   R9: 0000000006000000\n    R10: ffff88011796b8a0  R11: 0000000000000004  R12: ffff88010391ed00\n    R13: 0000000000000000  R14: ffff880666e45898  R15: ffff88011796b890\n    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018\n    [ffff880666e45838] _raw_write_lock_bh at ffffffff81450b39\n    [ffff880666e45858] __ip6_ins_rt at ffffffff813ed8c1\n    [ffff880666e45888] ip6_ins_rt at ffffffff813eef58\n    [ffff880666e458b8] rt6_redirect at ffffffff813f0b84\n    [ffff880666e45958] ndisc_rcv at ffffffff813f95d8\n    [ffff880666e45a08] icmpv6_rcv at ffffffff814000e8\n    [ffff880666e45ae8] ip6_input_finish at ffffffff813e43bb\n    [ffff880666e45b38] ip6_input at ffffffff813e4b08\n    [ffff880666e45b68] ipv6_rcv at ffffffff813e4969\n    [ffff880666e45bc8] __netif_receive_skb at ffffffff8135158a\n    [ffff880666e45c38] dev_gro_receive at ffffffff81351cb0\n    [ffff880666e45c78] napi_gro_receive at ffffffff81351fc5\n    [ffff880666e45cb8] tg3_rx at ffffffffa0bfb354 [tg]\n    [ffff880666e45d88] tg3_poll_work at ffffffffa0c07857 [tg]\n    [ffff880666e45e18] tg3_poll_msix at ffffffffa0c07d1b [tg]\n    [ffff880666e45e68] net_rx_action at ffffffff81352219\n    [ffff880666e45ec8] __do_softirq at ffffffff8103e5a1\n    [ffff880666e45f38] call_softirq at ffffffff81459c4c\n    [ffff880666e45f50] do_softirq at ffffffff8100413d\n    [ffff880666e45f80] do_IRQ at ffffffff81003cce\nThis happened when ip6_route_redirect found a rt which was set\nblackhole, the rt had a NULL rt6i_table argument which is accessed by\n__ip6_ins_rt() when trying to lock rt6i_table->tb6_lock caused a BUG:\n\"BUG: unable to handle kernel NULL pointer\"\n\nSigned-off-by: Weilong Chen <chenweilong@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/9a6fbaeb68f43f252c204e2ecf87a5d984b35a9d"},{"sha":"b1113711799e3b7dfa4ca18d9a873245112996a9","author":{"email":"94b5a4e124834aac3a4f84933f50b95d981df78b@gmail.com","name":"Alexander Ploumistos"},"message":"Bluetooth: ath3k: Add support Atheros AR5B195 combo Mini PCIe card\n\ncommit 2eeff0b4317a02f0e281df891d990194f0737aae upstream.\n\nAdd 04f2:aff1 to ath3k.c supported devices list and btusb.c blacklist, so\nthat the device can load the ath3k firmware and re-enumerate itself as an\nAR3011 device.\n\nT:  Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12   MxCh= 0\nD:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1\nP:  Vendor=04f2 ProdID=aff1 Rev= 0.01\nC:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA\nI:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms\nE:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms\nE:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms\nI:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms\nI:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms\nI:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms\nI:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms\nI:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms\nI:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb\nE:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms\nE:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms\n\nSigned-off-by: Alexander Ploumistos <alexpl@fedoraproject.org>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/b1113711799e3b7dfa4ca18d9a873245112996a9"},{"sha":"a76338a925c7647c6f7840eb36c9c85265e51df0","author":{"email":"bcbf172338421f26297a2592698edf8cc84ecbef@microsoft.com","name":"K. Y. Srinivasan"},"message":"Drivers: hv: vmbus: Fix a bug in the error path in vmbus_open()\n\ncommit 40384e4bbeb9f2651fe9bffc0062d9f31ef625bf upstream.\n\nCorrectly rollback state if the failure occurs after we have handed over\nthe ownership of the buffer to the host.\n\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/a76338a925c7647c6f7840eb36c9c85265e51df0"},{"sha":"4d2837d5dd82474f3f4eab26e1cab49172084b6f","author":{"email":"4452d71687b6bc2c9389c3349fdc17fbd73b833b@queasysnail.net","name":"Sabrina Dubroca"},"message":"e1000: add dummy allocator to fix race condition between mtu change and netpoll\n\ncommit 08e8331654d1d7b2c58045e549005bc356aa7810 upstream.\n\nThere is a race condition between e1000_change_mtu's cleanups and\nnetpoll, when we change the MTU across jumbo size:\n\nChanging MTU frees all the rx buffers:\n    e1000_change_mtu -> e1000_down -> e1000_clean_all_rx_rings ->\n        e1000_clean_rx_ring\n\nThen, close to the end of e1000_change_mtu:\n    pr_info -> ... -> netpoll_poll_dev -> e1000_clean ->\n        e1000_clean_rx_irq -> e1000_alloc_rx_buffers -> e1000_alloc_frag\n\nAnd when we come back to do the rest of the MTU change:\n    e1000_up -> e1000_configure -> e1000_configure_rx ->\n        e1000_alloc_jumbo_rx_buffers\n\nalloc_jumbo finds the buffers already != NULL, since data (shared with\npage in e1000_rx_buffer->rxbuf) has been re-alloc'd, but it's garbage,\nor at least not what is expected when in jumbo state.\n\nThis results in an unusable adapter (packets don't get through), and a\nNULL pointer dereference on the next call to e1000_clean_rx_ring\n(other mtu change, link down, shutdown):\n\nBUG: unable to handle kernel NULL pointer dereference at           (null)\nIP: [<ffffffff81194d6e>] put_compound_page+0x7e/0x330\n\n    [...]\n\nCall Trace:\n [<ffffffff81195445>] put_page+0x55/0x60\n [<ffffffff815d9f44>] e1000_clean_rx_ring+0x134/0x200\n [<ffffffff815da055>] e1000_clean_all_rx_rings+0x45/0x60\n [<ffffffff815df5e0>] e1000_down+0x1c0/0x1d0\n [<ffffffff811e2260>] ? deactivate_slab+0x7f0/0x840\n [<ffffffff815e21bc>] e1000_change_mtu+0xdc/0x170\n [<ffffffff81647050>] dev_set_mtu+0xa0/0x140\n [<ffffffff81664218>] do_setlink+0x218/0xac0\n [<ffffffff814459e9>] ? nla_parse+0xb9/0x120\n [<ffffffff816652d0>] rtnl_newlink+0x6d0/0x890\n [<ffffffff8104f000>] ? kvm_clock_read+0x20/0x40\n [<ffffffff810a2068>] ? sched_clock_cpu+0xa8/0x100\n [<ffffffff81663802>] rtnetlink_rcv_msg+0x92/0x260\n\nBy setting the allocator to a dummy version, netpoll can't mess up our\nrx buffers.  The allocator is set back to a sane value in\ne1000_configure_rx.\n\nFixes: edbbb3ca1077 (\"e1000: implement jumbo receive with partial descriptors\")\nSigned-off-by: Sabrina Dubroca <sd@queasysnail.net>\nTested-by: Aaron Brown <aaron.f.brown@intel.com>\nSigned-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/4d2837d5dd82474f3f4eab26e1cab49172084b6f"},{"sha":"cd440e0c3ff86c3dbc7bffea5fe7a3f083287880","author":{"email":"f287211da676ffdf91aea974631e3d58cbf5cace@linux.vnet.ibm.com","name":"Ekaterina Tumanova"},"message":"KVM: s390: Zero out current VMDB of STSI before including level3 data.\n\ncommit b75f4c9afac2604feb971441116c07a24ecca1ec upstream.\n\ns390 documentation requires words 0 and 10-15 to be reserved and stored as\nzeros. As we fill out all other fields, we can memset the full structure.\n\nSigned-off-by: Ekaterina Tumanova <tumanova@linux.vnet.ibm.com>\nReviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>\nSigned-off-by: Christian Borntraeger <borntraeger@de.ibm.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/cd440e0c3ff86c3dbc7bffea5fe7a3f083287880"},{"sha":"1c1a16a300f20cad61127a8ced4289c1bfaa3999","author":{"email":"94dddeeef08b001e003cce128ddc162a4e2c6cd2@ti.com","name":"Felipe Balbi"},"message":"usb: musb: core: fix TX/RX endpoint order\n\ncommit e3c93e1a3f35be4cf1493d3ccfb0c6d9209e4922 upstream.\n\nAs per Mentor Graphics' documentation, we should\nalways handle TX endpoints before RX endpoints.\n\nThis patch fixes that error while also updating\nsome hard-to-read comments which were scattered\naround musb_interrupt().\n\nThis patch should be backported as far back as\npossible since this error has been in the driver\nsince it's conception.\n\nSigned-off-by: Felipe Balbi <balbi@ti.com>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/1c1a16a300f20cad61127a8ced4289c1bfaa3999"},{"sha":"019114ceb62948be1645fcf47b09979269cf794a","author":{"email":"53ccad33e0625915318fb3bc832e5c1c413d1294@tkos.co.il","name":"Baruch Siach"},"message":"pinctrl: remove maxpin from documentation\n\ncommit 939417bd8b909ae34a3b2106531594f5115eaea5 upstream.\n\nstruct pinctrl_desc does not contain the maxpin member since commit 0d2006bbf0\n(pinctrl: remove unnecessary max pin number).\n\nFixes: 0d2006bbf0 ('pinctrl: remove unnecessary max pin number')\nSigned-off-by: Baruch Siach <baruch@tkos.co.il>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/019114ceb62948be1645fcf47b09979269cf794a"},{"sha":"ed53cbd0af77a73171d92cda1d379b02332e355e","author":{"email":"1a8531307367602b8284517edb33d53d54e5ce8e@samsung.com","name":"Krzysztof Kozlowski"},"message":"compal-laptop: Check return value of power_supply_register\n\ncommit 1915a718b1872edffcb13e5436a9f7302d3d36f0 upstream.\n\nThe return value of power_supply_register() call was not checked and\neven on error probe() function returned 0. If registering failed then\nduring unbind the driver tried to unregister power supply which was not\nactually registered.\n\nThis could lead to memory corruption because power_supply_unregister()\nunconditionally cleans up given power supply.\n\nFix this by checking return status of power_supply_register() call. In\ncase of failure, clean up sysfs entries and fail the probe.\n\nSigned-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nFixes: 9be0fcb5ed46 (\"compal-laptop: add JHL90, battery & hwmon interface\")\nSigned-off-by: Sebastian Reichel <sre@kernel.org>\n[lizf: Backported to 3.4: there's no \"remove\" label. Do cleanup inside if block]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/ed53cbd0af77a73171d92cda1d379b02332e355e"},{"sha":"5cee91e968a1da2c06e3e8555c5ff47d80b87c8b","author":{"email":"53ccad33e0625915318fb3bc832e5c1c413d1294@tkos.co.il","name":"Baruch Siach"},"message":"pinctrl: remove doc mention of the enable/disable API\n\ncommit b18104c00089c73f2b70790765d40424a4f9b65f upstream.\n\nThis API has changed in commit 6e5e959dde0 (pinctrl: API changes to support\nmultiple states per device).\n\nFixes: 6e5e959dde0 ('pinctrl: API changes to support multiple states per device')\nCc: Stephen Warren <swarren@nvidia.com>\nSigned-off-by: Baruch Siach <baruch@tkos.co.il>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/5cee91e968a1da2c06e3e8555c5ff47d80b87c8b"},{"sha":"5fbb6bf00e864ea6c1c5c623db09bc634f61b814","author":{"email":"53ccad33e0625915318fb3bc832e5c1c413d1294@tkos.co.il","name":"Baruch Siach"},"message":"pinctrl: fix example .get_group_pins implementation signature\n\ncommit 838d030bda9e2da5f9dcf7251f4e117c6258cb2f upstream.\n\nThe callback function signature has changed in commit a5818a8bd0 (pinctrl:\nget_group_pins() const fixes)\n\nFixes: a5818a8bd0 ('pinctrl: get_group_pins() const fixes')\nCc: Stephen Warren <swarren@nvidia.com>\nSigned-off-by: Baruch Siach <baruch@tkos.co.il>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/5fbb6bf00e864ea6c1c5c623db09bc634f61b814"},{"sha":"377bd9bd65d31bef5ee4345fc7c15f13dbf66c8a","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"drm/radeon: fix doublescan modes (v2)\n\ncommit fd99a0943ffaa0320ea4f69d09ed188f950c0432 upstream.\n\nUse the correct flags for atom.\n\nv2: handle DRM_MODE_FLAG_DBLCLK\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/377bd9bd65d31bef5ee4345fc7c15f13dbf66c8a"},{"sha":"5f37f495354f63b8e929f5c4e60fe4e3753c06eb","author":{"email":"c01a8c815a4ad165fff2d1c0d35ddf5b16bd3d7b@freescale.com","name":"Peter Chen"},"message":"usb: common: otg-fsm: only signal connect after switching to peripheral\n\ncommit 990919cad55a8c38fc73b0a6a0c9e5e4e927a5f8 upstream.\n\nWe should signal connect (pull up dp) after we have already\nat peripheral mode, otherwise, the dp may be toggled due to\nwe reset controller or do disconnect during the initialization\nfor peripheral, then, the host may be confused during the\nenumeration, eg, it finds the reset can't succeed, but the\ndevice is still there, see below error message.\n\nhub 1-0:1.0: USB hub found\nhub 1-0:1.0: 1 port detected\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: cannot reset port 1 (err = -32)\nhub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?\nhub 1-0:1.0: unable to enumerate USB device on port 1\n\nFixes: the issue existed when the otg fsm code was added.\nSigned-off-by: Peter Chen <peter.chen@freescale.com>\nSigned-off-by: Felipe Balbi <balbi@ti.com>\n[lizf: Backported to 3.4:\n - adjust filename\n - adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/5f37f495354f63b8e929f5c4e60fe4e3753c06eb"},{"sha":"c0a50fc107ca37cd51f9c472d34a430fe7bfb2fe","author":{"email":"207334009e4fa4f29d6a2e7d7bc3efb21d7c7c0e@gmx.de","name":"Sergej Sawazki"},"message":"ASoC: wm8741: Fix rates constraints values\n\ncommit 8787041d9bb832b9449b1eb878cedcebce42c61a upstream.\n\nThe WM8741 DAC supports the following typical audio sampling rates:\n  44.1kHz, 88.2kHz, 176.4kHz (eg: with a master clock of 22.5792MHz)\n  32kHz, 48kHz, 96kHz, 192kHz (eg: with a master clock of 24.576MHz)\n\nFor the rates lists, we should use 82000 instead of 88235, 176400\ninstead of 1764000 and 192000 instead of 19200 (seems to be a typo).\n\nSigned-off-by: Sergej Sawazki <ce3a@gmx.de>\nAcked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/c0a50fc107ca37cd51f9c472d34a430fe7bfb2fe"},{"sha":"3332e3d816fc023e8595ca70b72bf4d03dc67497","author":{"email":"bfee72d94d376f4e00f72b756466867d7f9eb24e@suse.de","name":"Oliver Neukum"},"message":"cdc-wdm: fix endianness bug in debug statements\n\ncommit 323ece54e0761198946ecd0c2091f1d2bfdfcb64 upstream.\n\nValues directly from descriptors given in debug statements\nmust be converted to native endianness.\n\nSigned-off-by: Oliver Neukum <oneukum@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/3332e3d816fc023e8595ca70b72bf4d03dc67497"},{"sha":"058ee4d9f5d19172ee16e5a816f65b3e97327e5a","author":{"email":"551ae05ce198473af5b9da594240f54df5f81e31@gmail.com","name":"Sudip Mukherjee"},"message":"staging: panel: fix lcd type\n\ncommit 2c20d92dad5db6440cfa88d811b69fd605240ce4 upstream.\n\nthe lcd type as defined in the Kconfig is not matching in the code.\nas a result the rs, rw and en pins were getting interchanged.\nKconfig defines the value of PANEL_LCD to be 1 if we select custom\nconfiguration but in the code LCD_TYPE_CUSTOM is defined as 5.\n\nmy hardware is LCD_TYPE_CUSTOM, but the pins were assigned to it\nas pins of LCD_TYPE_OLD, and it was not working.\nNow values are corrected with referenece to the values defined in\nKconfig and it is working.\nchecked on JHD204A lcd with LCD_TYPE_CUSTOM configuration.\n\nSigned-off-by: Sudip Mukherjee <sudip@vectorindia.org>\nAcked-by: Willy Tarreau <w@1wt.eu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/058ee4d9f5d19172ee16e5a816f65b3e97327e5a"},{"sha":"9ef6369ce62c086c475891681e529f24b377241c","author":{"email":"ac73eed4b8a8c9127255a2696c52b2e7503720b8@gmail.com","name":"Brian Norris"},"message":"UBI: fix out of bounds write\n\ncommit d74adbdb9abf0d2506a6c4afa534d894f28b763f upstream.\n\nIf aeb->len >= vol->reserved_pebs, we should not be writing aeb into the\nPEB->LEB mapping.\n\nCaught by Coverity, CID #711212.\n\nSigned-off-by: Brian Norris <computersforpeace@gmail.com>\nSigned-off-by: Richard Weinberger <richard@nod.at>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/9ef6369ce62c086c475891681e529f24b377241c"},{"sha":"0513688a9526f55e3090630901aeed1c76ca7fc3","author":{"email":"ac73eed4b8a8c9127255a2696c52b2e7503720b8@gmail.com","name":"Brian Norris"},"message":"UBI: initialize LEB number variable\n\ncommit f16db8071ce18819fbd705ddcc91c6f392fb61f8 upstream.\n\nIn some of the 'out_not_moved' error paths, lnum may be used\nuninitialized. Don't ignore the warning; let's fix it.\n\nThis uninitialized variable doesn't have much visible effect in the end,\nsince we just schedule the PEB for erasure, and its LEB number doesn't\nreally matter (it just gets printed in debug messages). But let's get it\nstraight anyway.\n\nCoverity CID #113449\n\nSigned-off-by: Brian Norris <computersforpeace@gmail.com>\nSigned-off-by: Richard Weinberger <richard@nod.at>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/0513688a9526f55e3090630901aeed1c76ca7fc3"},{"sha":"89873945d59c9b492bbbe8c636f851f633247046","author":{"email":"ac73eed4b8a8c9127255a2696c52b2e7503720b8@gmail.com","name":"Brian Norris"},"message":"UBI: fix check for \"too many bytes\"\n\ncommit 299d0c5b27346a77a0777c993372bf8777d4f2e5 upstream.\n\nThe comparison from the previous line seems to have been erroneously\n(partially) copied-and-pasted onto the next. The second line should be\nchecking req.bytes, not req.lnum.\n\nCoverity CID #139400\n\nSigned-off-by: Brian Norris <computersforpeace@gmail.com>\n[rw: Fixed comparison]\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/89873945d59c9b492bbbe8c636f851f633247046"},{"sha":"a96bd4f8531509f9889d6b05142e24fbbee58995","author":{"email":"50c3c575ce2bb12c45e20736ce59e86fe81915b4@ti.com","name":"Nishanth Menon"},"message":"C6x: time: Ensure consistency in __init\n\ncommit f4831605f2dacd12730fe73961c77253cc2ea425 upstream.\n\ntime_init invokes timer64_init (which is __init annotation)\nsince all of these are invoked at init time, lets maintain\nconsistency by ensuring time_init is marked appropriately\nas well.\n\nThis fixes the following warning with CONFIG_DEBUG_SECTION_MISMATCH=y\n\nWARNING: vmlinux.o(.text+0x3bfc): Section mismatch in reference from the function time_init() to the function .init.text:timer64_init()\nThe function time_init() references\nthe function __init timer64_init().\nThis is often because time_init lacks a __init\nannotation or the annotation of timer64_init is wrong.\n\nFixes: 546a39546c64 (\"C6X: time management\")\nSigned-off-by: Nishanth Menon <nm@ti.com>\nSigned-off-by: Mark Salter <msalter@redhat.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/a96bd4f8531509f9889d6b05142e24fbbee58995"},{"sha":"7fd83f326fb8d0da3f59f704fd6bb27e457aa9df","author":{"email":"bcbf172338421f26297a2592698edf8cc84ecbef@microsoft.com","name":"K. Y. Srinivasan"},"message":"Drivers: hv: vmbus: Don't wait after requesting offers\n\ncommit 73cffdb65e679b98893f484063462c045adcf212 upstream.\n\nDon't wait after sending request for offers to the host. This wait is\nunnecessary and simply adds 5 seconds to the boot time.\n\nSigned-off-by: K. Y. Srinivasan <kys@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/CyanogenMod/android_kernel_motorola_msm8960dt-common/commits/7fd83f326fb8d0da3f59f704fd6bb27e457aa9df"}]}