{"push_id":768858878,"size":36,"distinct_size":36,"ref":"refs/heads/lollipop-caf","head":"b6ddd410f9db56991c961b841b32c690544cef72","before":"a32a39485274fe7dcde3bb0aad47e879833cad91","commits":[{"sha":"444559ee166663e4024c8e436cab2ee5eef3764c","author":{"email":"e9e18c12cd15ca63116099b02663c9e3d043a667@opensource.altera.com","name":"Thor Thayer"},"message":"spi: dw: Fix dynamic speed change.\n\ncommit 0a8727e69778683495058852f783eeda141a754e upstream.\n\nAn IOCTL call that calls spi_setup() and then dw_spi_setup() will\noverwrite the persisted last transfer speed. On each transfer, the\nSPI speed is compared to the last transfer speed to determine if the\nclock divider registers need to be updated (did the speed change?).\nThis bug was observed with the spidev driver using spi-config to\nupdate the max transfer speed.\n\nThis fix: Don't overwrite the persisted last transaction clock speed\nwhen updating the SPI parameters in dw_spi_setup(). On the next\ntransaction, the new speed won't match the persisted last speed\nand the hardware registers will be updated.\nOn initialization, the persisted last transaction clock\nspeed will be 0 but will be updated after the first SPI\ntransaction.\n\nMove zeroed clock divider check into clock change test because\nchip->clk_div is zero on startup and would cause a divide-by-zero\nerror. The calculation was wrong as well (can't support odd #).\n\nReported-by: Vlastimil Setka <setka@vsis.cz>\nSigned-off-by: Vlastimil Setka <setka@vsis.cz>\nSigned-off-by: Thor Thayer <tthayer@opensource.altera.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/444559ee166663e4024c8e436cab2ee5eef3764c"},{"sha":"afdf9197743e8ba8e21ad08ae14549f7e8960e66","author":{"email":"105b2b8d73763347e9cf8984eec31fd1459b5cc0@gmail.com","name":"Preston Fick"},"message":"USB: serial: cp210x: add IDs for CEL MeshConnect USB Stick\n\ncommit ffcfe30ebd8dd703d0fc4324ffe56ea21f5479f4 upstream.\n\nSigned-off-by: Preston Fick <pffick@gmail.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/afdf9197743e8ba8e21ad08ae14549f7e8960e66"},{"sha":"1d1a612f175d7c225b52a50a8774201d62e203ad","author":{"email":"b540d48ac5dcedc87bda0ad9fa97deb9caba671e@intel.com","name":"Cristina Ciocan"},"message":"iio: Fix IIO_EVENT_CODE_EXTRACT_DIR bit mask\n\ncommit ccf54555da9a5e91e454b909ca6a5303c7d6b910 upstream.\n\nThe direction field is set on 7 bits, thus we need to AND it with 0111 111 mask\nin order to retrieve it, that is 0x7F, not 0xCF as it is now.\n\nFixes: ade7ef7ba (staging:iio: Differential channel handling)\nSigned-off-by: Cristina Ciocan <cristina.ciocan@intel.com>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/1d1a612f175d7c225b52a50a8774201d62e203ad"},{"sha":"c742eaef0612e3e598663698df7bdcf1bf0c617d","author":{"email":"5f82f8f1c6cd0e18143273e129a1829fd8958b37@matrixorbital.ca","name":"Troy Clark"},"message":"usb: serial: ftdi_sio: add PIDs for Matrix Orbital products\n\ncommit 204ec6e07ea7aff863df0f7c53301f9cbbfbb9d3 upstream.\n\nAdd PIDs for new Matrix Orbital GTT series products.\n\nSigned-off-by: Troy Clark <tclark@matrixorbital.ca>\n[johan: shorten commit message ]\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/c742eaef0612e3e598663698df7bdcf1bf0c617d"},{"sha":"44346ee326d86208f88f6e0033db08259f0c72d5","author":{"email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org","name":"Johan Hovold"},"message":"USB: keyspan: fix tty line-status reporting\n\ncommit 5d1678a33c731b56e245e888fdae5e88efce0997 upstream.\n\nFix handling of TTY error flags, which are not bitmasks and must\nspecifically not be ORed together as this prevents the line discipline\nfrom recognising them.\n\nAlso insert null characters when reporting overrun errors as these are\nnot associated with the received character.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\n[lizf: Backported to 3.4:\n - s/&port->port/tty/\n - adjust context\n - adjust indentation]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/44346ee326d86208f88f6e0033db08259f0c72d5"},{"sha":"4728916c6c5150dfa5e94996eea8b761d8530d2c","author":{"email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org","name":"Johan Hovold"},"message":"USB: keyspan: fix overrun-error reporting\n\ncommit 855515a6d3731242d85850a206f2ec084c917338 upstream.\n\nFix reporting of overrun errors, which are not associated with a\ncharacter. Instead insert a null character and report only once.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\n[lizf: Backported to 3.4:\n - s/&port->port/tty\n - adjust context\n - adjust indentation]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/4728916c6c5150dfa5e94996eea8b761d8530d2c"},{"sha":"c6d5eb41ea585d9fbec42178474af3e482a1efe8","author":{"email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org","name":"Johan Hovold"},"message":"USB: ssu100: fix overrun-error reporting\n\ncommit 75bcbf29c284dd0154c3e895a0bd1ef0e796160e upstream.\n\nFix reporting of overrun errors, which should only be reported once\nusing the inserted null character.\n\nFixes: 6b8f1ca5581b (\"USB: ssu100: set tty_flags in ssu100_process_packet\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\n[lizf: Backported to 3.4:\n - adjust context\n - lookup tty using tty_port_tty_get()]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/c6d5eb41ea585d9fbec42178474af3e482a1efe8"},{"sha":"67ee1b8757f2b920ff65a4e1f87f96238e4b974c","author":{"email":"cc958843532c615cbd4920e868f78c7985331a5a@primarydata.com","name":"Trond Myklebust"},"message":"SUNRPC: Fix locking around callback channel reply receive\n\ncommit 093a1468b6edb0e568be7311b8d2228d205702db upstream.\n\nBoth xprt_lookup_rqst() and xprt_complete_rqst() require that you\ntake the transport lock in order to avoid races with xprt_transmit().\n\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nReviewed-by: Jeff Layton <jlayton@primarydata.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.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/DirtyUnicorns/android_kernel_motorola_ghost/commits/67ee1b8757f2b920ff65a4e1f87f96238e4b974c"},{"sha":"df3fe5c38f427f22bb824b13a76ca1e69fd04dba","author":{"email":"cc958843532c615cbd4920e868f78c7985331a5a@primarydata.com","name":"Trond Myklebust"},"message":"nfsd: Fix slot wake up race in the nfsv4.1 callback code\n\ncommit c6c15e1ed303ffc47e696ea1c9a9df1761c1f603 upstream.\n\nThe currect code for nfsd41_cb_get_slot() and nfsd4_cb_done() has no\nlocking in order to guarantee atomicity, and so allows for races of\nthe form.\n\nTask 1                                  Task 2\n======                                  ======\nif (test_and_set_bit(0) != 0) {\n                                        clear_bit(0)\n                                        rpc_wake_up_next(queue)\n        rpc_sleep_on(queue)\n        return false;\n}\n\nThis patch breaks the race condition by adding a retest of the bit\nafter the call to rpc_sleep_on().\n\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/df3fe5c38f427f22bb824b13a76ca1e69fd04dba"},{"sha":"de05e226cd685a95f8878956b3ce0c71c0454203","author":{"email":"954d0c936553fa022eb0631b7a3a263f1388ea3d@redhat.com","name":"Maurizio Lombardi"},"message":"bnx2fc: do not add shared skbs to the fcoe_rx_list\n\ncommit 01a4cc4d0cd6a836c7b923760e8eb1cbb6a47258 upstream.\n\nIn some cases, the fcoe_rx_list may contains multiple instances\nof the same skb (the so called \"shared skbs\").\n\nthe bnx2fc_l2_rcv thread is a loop that extracts a skb from the list,\nmodifies (and destroys) its content and then proceed to the next one.\nThe problem is that if the skb is shared, the remaining instances will\nbe corrupted.\n\nThe solution is to use skb_share_check() before adding the skb to the\nfcoe_rx_list.\n\n[ 6286.808725] ------------[ cut here ]------------\n[ 6286.808729] WARNING: at include/scsi/fc_frame.h:173 bnx2fc_l2_rcv_thread+0x425/0x450 [bnx2fc]()\n[ 6286.808748] Modules linked in: bnx2x(-) mdio dm_service_time bnx2fc cnic uio fcoe libfcoe 8021q garp stp mrp libfc llc scsi_transport_fc scsi_tgt sg iTCO_wdt iTCO_vendor_support coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel e1000e ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper ablk_helper ptp cryptd hpilo serio_raw hpwdt lpc_ich pps_core ipmi_si pcspkr mfd_core ipmi_msghandler shpchp pcc_cpufreq mperf nfsd auth_rpcgss nfs_acl lockd sunrpc dm_multipath xfs libcrc32c ata_generic pata_acpi sd_mod crc_t10dif crct10dif_common mgag200 syscopyarea sysfillrect sysimgblt i2c_algo_bit ata_piix drm_kms_helper ttm drm libata i2c_core hpsa dm_mirror dm_region_hash dm_log dm_mod [last unloaded: mdio]\n[ 6286.808750] CPU: 3 PID: 1304 Comm: bnx2fc_l2_threa Not tainted 3.10.0-121.el7.x86_64 #1\n[ 6286.808750] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013\n[ 6286.808752]  0000000000000000 000000000b36e715 ffff8800deba1e00 ffffffff815ec0ba\n[ 6286.808753]  ffff8800deba1e38 ffffffff8105dee1 ffffffffa05618c0 ffff8801e4c81888\n[ 6286.808754]  ffffe8ffff663868 ffff8801f402b180 ffff8801f56bc000 ffff8800deba1e48\n[ 6286.808754] Call Trace:\n[ 6286.808759]  [<ffffffff815ec0ba>] dump_stack+0x19/0x1b\n[ 6286.808762]  [<ffffffff8105dee1>] warn_slowpath_common+0x61/0x80\n[ 6286.808763]  [<ffffffff8105e00a>] warn_slowpath_null+0x1a/0x20\n[ 6286.808765]  [<ffffffffa054f415>] bnx2fc_l2_rcv_thread+0x425/0x450 [bnx2fc]\n[ 6286.808767]  [<ffffffffa054eff0>] ? bnx2fc_disable+0x90/0x90 [bnx2fc]\n[ 6286.808769]  [<ffffffff81085aef>] kthread+0xcf/0xe0\n[ 6286.808770]  [<ffffffff81085a20>] ? kthread_create_on_node+0x140/0x140\n[ 6286.808772]  [<ffffffff815fc76c>] ret_from_fork+0x7c/0xb0\n[ 6286.808773]  [<ffffffff81085a20>] ? kthread_create_on_node+0x140/0x140\n[ 6286.808774] ---[ end trace c6cdb939184ccb4e ]---\n\nSigned-off-by: Maurizio Lombardi <mlombard@redhat.com>\nAcked-by: Chad Dupuis <chad.dupuis@qlogic.com>\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/de05e226cd685a95f8878956b3ce0c71c0454203"},{"sha":"9c3512f2b44bef7f5fe2f1ea44a75a1126eb9eeb","author":{"email":"b6edad08270b2e4ffbcb0879e25a0e29a48c5275@gmail.com","name":"Dmitry Eremin-Solenikov"},"message":"ARM: 8216/1: xscale: correct auxiliary register in suspend/resume\n\ncommit ef59a20ba375aeb97b3150a118318884743452a8 upstream.\n\nAccording to the manuals I have, XScale auxiliary register should be\nreached with opc_2 = 1 instead of crn = 1. cpu_xscale_proc_init\ncorrectly uses c1, c0, 1 arguments, but cpu_xscale_do_suspend and\ncpu_xscale_do_resume use c1, c1, 0. Correct suspend/resume functions to\nalso use c1, c0, 1.\n\nThe issue was primarily noticed thanks to qemu reporing \"unsupported\ninstruction\" on the pxa suspend path. Confirmed in PXA210/250 and PXA255\nXScale Core manuals and in PXA270 and PXA320 Developers Guides.\n\nHarware tested by me on tosa (pxa255). Robert confirmed on pxa270 board.\n\nTested-by: Robert Jarzmik <robert.jarzmik@free.fr>\nSigned-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>\nAcked-by: Robert Jarzmik <robert.jarzmik@free.fr>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/9c3512f2b44bef7f5fe2f1ea44a75a1126eb9eeb"},{"sha":"121d05dd9394b768c8ea96ec785900290a64ecda","author":{"email":"2d4473c5e67eb83655334d4e9a7757f781607241@linux.intel.com","name":"Mathias Nyman"},"message":"USB: xhci: don't start a halted endpoint before its new dequeue is set\n\ncommit c3492dbfa1050debf23a5b5cd2bc7514c5b37896 upstream.\n\nA halted endpoint ring must first be reset, then move the ring\ndequeue pointer past the problematic TRB. If we start the ring too\nearly after reset, but before moving the dequeue pointer we\nwill end up executing the same problematic TRB again.\n\nAs we always issue a set transfer dequeue command after a reset\nendpoint command we can skip starting endpoint rings at reset endpoint\ncommand completion.\n\nWithout this fix we end up trying to handle the same faulty TD for\ncontol endpoints. causing timeout, and failing testusb ctrl_out write\ntests.\n\nFixes: e9df17e (USB: xhci: Correct assumptions about number of rings per endpoint.)\nTested-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.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/DirtyUnicorns/android_kernel_motorola_ghost/commits/121d05dd9394b768c8ea96ec785900290a64ecda"},{"sha":"8b84c5f7bb4eebff9b221246efe12afcc833ba11","author":{"email":"2d4473c5e67eb83655334d4e9a7757f781607241@linux.intel.com","name":"Mathias Nyman"},"message":"USB: xhci: Reset a halted endpoint immediately when we encounter a stall.\n\ncommit 8e71a322fdb127814bcba423a512914ca5bc6cf5 upstream.\n\nIf a device is halted and reuturns a STALL, then the halted endpoint\nneeds to be cleared both on the host and device side. The host\nside halt is cleared by issueing a xhci reset endpoint command. The device side\nis cleared with a ClearFeature(ENDPOINT_HALT) request, which should\nbe issued by the device driver if a URB reruen -EPIPE.\n\nPreviously we cleared the host side halt after the device side was cleared.\nTo make sure the host side halt is cleared in time we want to issue the\nreset endpoint command immedialtely when a STALL status is encountered.\n\nOtherwise we end up not following the specs and not returning -EPIPE\nseveral times in a row when trying to transfer data to a halted endpoint.\n\nFixes: bcef3fd (USB: xhci: Handle errors that cause endpoint halts.)\nTested-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.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/DirtyUnicorns/android_kernel_motorola_ghost/commits/8b84c5f7bb4eebff9b221246efe12afcc833ba11"},{"sha":"8c92b22375521aae8232d2a585b9c8c8d8b360e1","author":{"email":"0e8503a5d55e00d5d2190cff62ef5fd449aa2247@linux.intel.com","name":"Lu Baolu"},"message":"usb: xhci: rework root port wake bits if controller isn't allowed to wakeup\n\ncommit a1377e5397ab321e21b793ec8cd2b6f12bd3c718 upstream.\n\nWhen system is being suspended, if host device is not allowed to do wakeup,\nxhci_suspend() needs to clear all root port wake on bits. Otherwise, some\nplatforms may generate spurious wakeup, even if PCI PME# is disabled.\n\nThe initial commit ff8cbf250b44 (\"xhci: clear root port wake on bits\"),\nwhich also got into stable, turned out to not work correctly and had to\nbe reverted, and is now rewritten.\n\nSigned-off-by: Lu Baolu <baolu.lu@linux.intel.com>\nSuggested-by: Alan Stern <stern@rowland.harvard.edu>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\n[Mathias Nyman: reword commit message]\nSigned-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n[lizf: Backported to 3.4:\n - adjust context\n - drop changes to xhci_plat_suspend()]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/8c92b22375521aae8232d2a585b9c8c8d8b360e1"},{"sha":"723859bb8fc7512080a396587b7a56787556e941","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: hda - Limit 40bit DMA for AMD HDMI controllers\n\ncommit 413cbf469a19e7662ba5025695bf5a573927105a upstream.\n\nAMD/ATI HDMI controller chip models, we already have a filter to lower\nto 32bit DMA, but the rest are supposed to be working with 64bit\nalthough the hardware doesn't really work with 63bit but only with 40\nor 48bit DMA.  In this patch, we take 40bit DMA for safety for the\nAMD/ATI controllers as the graphics drivers does.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\n[lizf: Backported to 3.4:\n - adjust context\n - s/AZX_GCAP_640K/ICH6_GCAP_64OK]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/723859bb8fc7512080a396587b7a56787556e941"},{"sha":"8dd7d24c5fb754a5af51728781fcab6b9f99ef66","author":{"email":"13423a3f3006b5859cfceae66d59451f5eb4e205@iki.fi","name":"Aaro Koskinen"},"message":"MIPS: Loongson: Make platform serial setup always built-in.\n\ncommit 26927f76499849e095714452b8a4e09350f6a3b9 upstream.\n\nIf SERIAL_8250 is compiled as a module, the platform specific setup\nfor Loongson will be a module too, and it will not work very well.\nAt least on Loongson 3 it will trigger a build failure,\nsince loongson_sysconf is not exported to modules.\n\nFix by making the platform specific serial code always built-in.\n\nSigned-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>\nReported-by: Ralf Baechle <ralf@linux-mips.org>\nCc: linux-mips@linux-mips.org\nCc: Huacai Chen <chenhc@lemote.com>\nCc: Markos Chandras <Markos.Chandras@imgtec.com>\nPatchwork: https://patchwork.linux-mips.org/patch/8533/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/8dd7d24c5fb754a5af51728781fcab6b9f99ef66"},{"sha":"c8812191002e9ff3fef27cb35468f80493cc685b","author":{"email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com","name":"Hans de Goede"},"message":"usb-quirks: Add reset-resume quirk for MS Wireless Laser Mouse 6000\n\ncommit 263e80b43559a6103e178a9176938ce171b23872 upstream.\n\nThis wireless mouse receiver needs a reset-resume quirk to properly come\nout of reset.\n\nBugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1165206\nSigned-off-by: Hans de Goede <hdegoede@redhat.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/DirtyUnicorns/android_kernel_motorola_ghost/commits/c8812191002e9ff3fef27cb35468f80493cc685b"},{"sha":"6cf7e8ed3eb3f0678f22aff1d57fa30ace6b2eb7","author":{"email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","name":"Greg Kroah-Hartman"},"message":"Input: xpad - use proper endpoint type\n\ncommit a1f9a4072655843fc03186acbad65990cc05dd2d upstream.\n\nThe xpad wireless endpoint is not a bulk endpoint on my devices, but\nrather an interrupt one, so the USB core complains when it is submitted.\nI'm guessing that the author really did mean that this should be an\ninterrupt urb, but as there are a zillion different xpad devices out\nthere, let's cover out bases and handle both bulk and interrupt\nendpoints just as easily.\n\nSigned-off-by: \"Pierre-Loup A. Griffais\" <pgriffais@valvesoftware.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/6cf7e8ed3eb3f0678f22aff1d57fa30ace6b2eb7"},{"sha":"30a9e692b2c8c47c20f5badf09f5276feebd932b","author":{"email":"a59ffce977ae3d39bdc87f81ff88b229ad58db88@linux.vnet.ibm.com","name":"Laurent Dufour"},"message":"powerpc/pseries: Fix endiannes issue in RTAS call from xmon\n\ncommit 3b8a3c01096925a824ed3272601082289d9c23a5 upstream.\n\nOn pseries system (LPAR) xmon failed to enter when running in LE mode,\nsystem is hunging. Inititating xmon will lead to such an output on the\nconsole:\n\nSysRq : Entering xmon\ncpu 0x15: Vector: 0  at [c0000003f39ffb10]\n    pc: c00000000007ed7c: sysrq_handle_xmon+0x5c/0x70\n    lr: c00000000007ed7c: sysrq_handle_xmon+0x5c/0x70\n    sp: c0000003f39ffc70\n   msr: 8000000000009033\n  current = 0xc0000003fafa7180\n  paca    = 0xc000000007d75e80\t softe: 0\t irq_happened: 0x01\n    pid   = 14617, comm = bash\nBad kernel stack pointer fafb4b0 at eca7cc4\ncpu 0x15: Vector: 300 (Data Access) at [c000000007f07d40]\n    pc: 000000000eca7cc4\n    lr: 000000000eca7c44\n    sp: fafb4b0\n   msr: 8000000000001000\n   dar: 10000000\n dsisr: 42000000\n  current = 0xc0000003fafa7180\n  paca    = 0xc000000007d75e80\t softe: 0\t irq_happened: 0x01\n    pid   = 14617, comm = bash\ncpu 0x15: Exception 300 (Data Access) in xmon, returning to main loop\nxmon: WARNING: bad recursive fault on cpu 0x15\n\nThe root cause is that xmon is calling RTAS to turn off the surveillance\nwhen entering xmon, and RTAS is requiring big endian parameters.\n\nThis patch is byte swapping the RTAS arguments when running in LE mode.\n\nSigned-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":true,"url":"https://api.github.com/repos/DirtyUnicorns/android_kernel_motorola_ghost/commits/30a9e692b2c8c47c20f5badf09f5276feebd932b"},{"sha":"a04c1de432ac57266402203d428bffe29d5a5bcf","author":{"email":"c1b6782c4af8f0673da8923a0702a1832e5940f4@ffwll.ch","name":"Daniel Vetter"},"message":"drm/i915: Unlock panel even when LVDS is disabled\n\ncommit b0616c5306b342ceca07044dbc4f917d95c4f825 upstream.\n\nOtherwise we'll have backtraces in assert_panel_unlocked because the\nBIOS locks the register. In the reporter's case this regression was\nintroduced in\n\ncommit c31407a3672aaebb4acddf90944a114fa5c8af7b\nAuthor: Chris Wilson <chris@chris-wilson.co.uk>\nDate:   Thu Oct 18 21:07:01 2012 +0100\n\n    drm/i915: Add no-lvds quirk for Supermicro X7SPA-H\n\nReported-by: Alexey Orishko <alexey.orishko@gmail.com>\nCc: Alexey Orishko <alexey.orishko@gmail.com>\nCc: Chris Wilson <chris@chris-wilson.co.uk>\nCc: Francois Tigeot <ftigeot@wolfpond.org>\nSigned-off-by: Daniel Vetter <daniel.vetter@intel.com>\nTested-by: Alexey Orishko <alexey.orishko@gmail.com>\nSigned-off-by: Jani Nikula <jani.nikula@intel.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/DirtyUnicorns/android_kernel_motorola_ghost/commits/a04c1de432ac57266402203d428bffe29d5a5bcf"}]}