{"push_id":1073005967,"size":192,"distinct_size":0,"ref":"refs/heads/work/kemnade/wifi-sdio-fixes-v3","head":"2171b5f011bd07622b421147f7b6c0223dd67e2a","before":"b6fdc82ca0b05eeea6d2e784542b7c6429f6e283","commits":[{"sha":"ebf24414809200915b9ddf7f109bba7c278c8210","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@atomide.com","name":"Tony Lindgren"},"message":"ARM: OMAP2+: Use srst_udelay for USB on dm814x\n\nWithout this booting t410 can fail randomly with no output\ndepending on the .config options chosen. Enabling debug_ll\ncauses the problem to go away. I narrowed this down to USB\nby disabling one module at a time.\n\nAcked-by: Paul Walmsley <paul@pwsan.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/ebf24414809200915b9ddf7f109bba7c278c8210"},{"sha":"d30596737e8e7b2f1235d7ba20592b8309e3af04","author":{"email":"19c3937cc6350b6aea2b428d361ed7d63d59244a@gmail.com","name":"Cyan Ogilvie"},"message":"HID: wiimote: Fix wiimote mp scale linearization\n\nThe wiimote motion plus gyros use two scales to report fast and slow\nrotation - below 440 deg/s uses 8192/440 units / deg/s, and above uses\n8192/2000 units / deg/s.\n\nPreviously this driver attempted to linearize the two by scaling the fast\nrate by 18 and the slow by 9, but this results in a scale of\n8192*9/440 = ~167.564 for slow and 8192*18/2000 = 73.728 for fast.\n\nCorrect the fast motion scale factor so that both report ~167.564\nunits / deg/s\n\nSigned-off-by: Cyan Ogilvie <cyan.ogilvie@gmail.com>\nReviewed-by: David Herrmann <dh.herrmann@gmail.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/d30596737e8e7b2f1235d7ba20592b8309e3af04"},{"sha":"972e6a993f278b416a8ee3ec65475724fc36feb2","author":{"email":"75ea6bb7bfc1186f92d26164de5f9268c9a45b59@rowland.harvard.edu","name":"Alan Stern"},"message":"HID: usbhid: fix inconsistent reset/resume/reset-resume behavior\n\nThe usbhid driver has inconsistently duplicated code in its post-reset,\nresume, and reset-resume pathways.\n\n\treset-resume doesn't check HID_STARTED before trying to\n\trestart the I/O queues.\n\n\tresume fails to clear the HID_SUSPENDED flag if HID_STARTED\n\tisn't set.\n\n\tresume calls usbhid_restart_queues() with usbhid->lock held\n\tand the others call it without holding the lock.\n\nThe first item in particular causes a problem following a reset-resume\nif the driver hasn't started up its I/O.  URB submission fails because\nusbhid->urbin is NULL, and this triggers an unending reset-retry loop.\n\nThis patch fixes the problem by creating a new subroutine,\nhid_restart_io(), to carry out all the common activities.  It also\nadds some checks that were missing in the original code:\n\n\tAfter a reset, there's no need to clear any halted endpoints.\n\n\tAfter a resume, if a reset is pending there's no need to\n\trestart any I/O until the reset is finished.\n\n\tAfter a resume, if the interrupt-IN endpoint is halted there's\n\tno need to submit the input URB until the halt has been\n\tcleared.\n\nSigned-off-by: Alan Stern <stern@rowland.harvard.edu>\nReported-by: Daniel Fraga <fragabr@gmail.com>\nTested-by: Daniel Fraga <fragabr@gmail.com>\nCC: <stable@vger.kernel.org>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/972e6a993f278b416a8ee3ec65475724fc36feb2"},{"sha":"3ca4a238106dedc285193ee47f494a6584b6fd2f","author":{"email":"c1574519d727edaf2e16b260e452051ef77bf018@ti.com","name":"Lokesh Vutla"},"message":"ARM: OMAP2+: hwmod: Fix updating of sysconfig register\n\nCommit 127500ccb766f (\"ARM: OMAP2+: Only write the sysconfig on idle\nwhen necessary\") talks about verification of sysconfig cache value before\nupdating it, only during idle path. But the patch is adding the\nverification in the enable path. So, adding the check in a proper place\nas per the commit description.\n\nNot keeping this check during enable path as there is a chance of losing\ncontext and it is safe to do on idle as the context of the register will\nnever be lost while the device is active.\n\nSigned-off-by: Lokesh Vutla <lokeshvutla@ti.com>\nAcked-by: Tero Kristo <t-kristo@ti.com>\nCc: Jon Hunter <jonathanh@nvidia.com>\nCc: <stable@vger.kernel.org> # 3.12+\nFixes: commit 127500ccb766 \"ARM: OMAP2+: Only write the sysconfig on idle when necessary\"\n[paul@pwsan.com: appears to have been caused by my own mismerge of the\n originally posted patch]\nSigned-off-by: Paul Walmsley <paul@pwsan.com>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/3ca4a238106dedc285193ee47f494a6584b6fd2f"},{"sha":"591b1d8d86074ac3a3163d89bcfe7b232cf83902","author":{"email":"71bcd3d88361b22cd828f9a350d19d8775f56d4e@linux.intel.com","name":"Dave Hansen"},"message":"x86/mm/pkeys: Add missing Documentation\n\nStefan Richter noticed that the X86_INTEL_MEMORY_PROTECTION_KEYS option\nin arch/x86/Kconfig references Documentation/x86/protection-keys.txt,\nbut the file does not exist.\n\nThis is a patch merging mishap: the final (v8) version of the pkeys\nseries did not include the documentation patch 32 and v7 included.\nAdd it now.\n\nReported-by: Stefan Richter <stefanr@s5r6.in-berlin.de>\nSigned-off-by: Dave Hansen <dave.hansen@linux.intel.com>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Brian Gerst <brgerst@gmail.com>\nCc: Dave Hansen <dave@sr71.net>\nCc: Denys Vlasenko <dvlasenk@redhat.com>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: linux-mm@kvack.org\nLink: http://lkml.kernel.org/r/20151214190634.426BEE41@viggo.jf.intel.com\n[ Added changelog. ]\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/591b1d8d86074ac3a3163d89bcfe7b232cf83902"},{"sha":"6d92bc9d483aa1751755a66fee8fb39dffb088c0","author":{"email":"e6b730070cb8ff71eb70dcaf29e26324d883b33b@gmail.com","name":"H.J. Lu"},"message":"x86/build: Build compressed x86 kernels as PIE\n\nThe 32-bit x86 assembler in binutils 2.26 will generate R_386_GOT32X\nrelocation to get the symbol address in PIC.  When the compressed x86\nkernel isn't built as PIC, the linker optimizes R_386_GOT32X relocations\nto their fixed symbol addresses.  However, when the compressed x86\nkernel is loaded at a different address, it leads to the following\nload failure:\n\n  Failed to allocate space for phdrs\n\nduring the decompression stage.\n\nIf the compressed x86 kernel is relocatable at run-time, it should be\ncompiled with -fPIE, instead of -fPIC, if possible and should be built as\nPosition Independent Executable (PIE) so that linker won't optimize\nR_386_GOT32X relocation to its fixed symbol address.\n\nOlder linkers generate R_386_32 relocations against locally defined\nsymbols, _bss, _ebss, _got and _egot, in PIE.  It isn't wrong, just less\noptimal than R_386_RELATIVE.  But the x86 kernel fails to properly handle\nR_386_32 relocations when relocating the kernel.  To generate\nR_386_RELATIVE relocations, we mark _bss, _ebss, _got and _egot as\nhidden in both 32-bit and 64-bit x86 kernels.\n\nTo build a 64-bit compressed x86 kernel as PIE, we need to disable the\nrelocation overflow check to avoid relocation overflow errors. We do\nthis with a new linker command-line option, -z noreloc-overflow, which\ngot added recently:\n\n commit 4c10bbaa0912742322f10d9d5bb630ba4e15dfa7\n Author: H.J. Lu <hjl.tools@gmail.com>\n Date:   Tue Mar 15 11:07:06 2016 -0700\n\n    Add -z noreloc-overflow option to x86-64 ld\n\n    Add -z noreloc-overflow command-line option to the x86-64 ELF linker to\n    disable relocation overflow check.  This can be used to avoid relocation\n    overflow check if there will be no dynamic relocation overflow at\n    run-time.\n\nThe 64-bit compressed x86 kernel is built as PIE only if the linker supports\n-z noreloc-overflow.  So far 64-bit relocatable compressed x86 kernel\nboots fine even when it is built as a normal executable.\n\nSigned-off-by: H.J. Lu <hjl.tools@gmail.com>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Brian Gerst <brgerst@gmail.com>\nCc: Denys Vlasenko <dvlasenk@redhat.com>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: linux-kernel@vger.kernel.org\n[ Edited the changelog and comments. ]\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/6d92bc9d483aa1751755a66fee8fb39dffb088c0"},{"sha":"ea36ae09105b7688225c02d33f1f3213299360f6","author":{"email":"94755a79aca753e683bb6d0e796d473b797056eb@fedoraproject.org","name":"Josh Boyer"},"message":"HID: lenovo: Don't use stack variables for DMA buffers\n\nThe lenovo_send_cmd_cptkbd function uses a stack variable to submit\ncommands via hid_hw_raw_request.  Eventually this gets to the\nusb_hcd_map_urb_for_dma function, which causes a warning to be thrown\nif the CONFIG_DMA_API_DEBUG option is enabled.\n\nFix this by allocating a temporary buffer instead.\n\n[jkosina@suse.cz: no need to NULL-initialize buf, spotted by Benjamin]\nReported-by: lejeczek <peljasz@yahoo.co.uk>\nSigned-off-by: Josh Boyer <jwboyer@fedoraproject.org>\nReviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/ea36ae09105b7688225c02d33f1f3213299360f6"},{"sha":"580549ef6b3e3fb3b958de490ca99f43a089a2cf","author":{"email":"7a0e50e3f6a0939db82b6a8a423c08a163896f41@redhat.com","name":"Benjamin Tissoires"},"message":"HID: wacom: fix Bamboo ONE oops\n\nLooks like recent changes in the Wacom driver made the Bamboo ONE crashes.\nThe tablet behaves as if it was a regular Bamboo device with pen, touch\nand pad, but there is no physical pad connected to it.\nThe weird part is that the pad is still sending events and given that\nthere is no input node connected to it, we get  anull pointer exception.\n\nLink: https://bugzilla.redhat.com/show_bug.cgi?id=1317116\n\nSigned-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>\nAcked-by: Ping Cheng <pingc@wacom.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/580549ef6b3e3fb3b958de490ca99f43a089a2cf"},{"sha":"4c35430ad18f5a034302cb90e559ede5a27f93b9","author":{"email":"94b2a0a74cb42a2dd0cf1b763601af7f13907aa9@free.fr","name":"Robert Jarzmik"},"message":"ARM: pxa: fix the number of DMA requestor lines\n\nThe number of requestor lines was clamped to 0 for all pxa architectures\nin the requestor declaration. Fix this by using the value.\n\nFixes: 72b195cb7162 (\"ARM: pxa: add the number of DMA requestor lines\")\nSigned-off-by: Robert Jarzmik <robert.jarzmik@free.fr>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/4c35430ad18f5a034302cb90e559ede5a27f93b9"},{"sha":"16b02d711f4059b8338ef967064195b47cae65ea","author":{"email":"1c24ea00d8ce704dffa3997c81be1310fc2bbac6@libc.org","name":"Rich Felker"},"message":"Merge tag 'v4.6-rc1'\n\nLinux 4.6-rc1","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/16b02d711f4059b8338ef967064195b47cae65ea"},{"sha":"ef21b32a60fbfdf2370465e52036c1c5ed1f6b43","author":{"email":"1c24ea00d8ce704dffa3997c81be1310fc2bbac6@libc.org","name":"Rich Felker"},"message":"sh: fix smp-shx3 build regression from removal of arch localtimer\n\nThe removal was not complete and left behind one reference to a\nremoved function in smp-shx3.c. For completeness, also remove\ndeclarations for functions that were removed.\n\nFixes: 45624ac38926 \"sh: remove arch-specific localtimer and use generic one\"\nReported-by: Geert Uytterhoeven <geert@linux-m68k.org>\nSigned-off-by: Rich Felker <dalias@libc.org>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/ef21b32a60fbfdf2370465e52036c1c5ed1f6b43"},{"sha":"427b1d3faa448212337c599e5454325af64e9a8e","author":{"email":"9cd9d802d23c0ed5e224beabf4ae4a5c478746ef@linaro.org","name":"Linus Walleij"},"message":"ARM: u8500_defconfig: turn on the Synaptics RMI4 driver\n\nThe Ux500 boards may have an RMI4 unit, and the DT fragments for\nthem have been merged upstream. Add it to the defconfig.\n\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/427b1d3faa448212337c599e5454325af64e9a8e"},{"sha":"e6cc3be552f9fedf5fa6b37c285d7d27ffc08b03","author":{"email":"1bc8cf2274d8680f3a9b88ac7b7d2a9e0d1d4ca2@broadcom.com","name":"Jayachandran C"},"message":"arm64: dts: vulcan: Update PCI ranges\n\nThe PCI memory windows available in vulcan.dtsi are limited to 128MB\nfor 32-bit BARs, and 4GB for 64-bit BARs. Given the memory mapped IO\nspace available in arm64, these windows can be increased substantially\nto support more use cases.\n\nThe change increases the 32-bit window to 256MB and the 64-bit window\nto 128 GB. The firmware on vulcan boards will use these ranges as well.\n\nPCI IO windows are not supported on Vulcan, so remove them instead of\nkeeping an unused value.\n\nSigned-off-by: Jayachandran C <jchandra@broadcom.com>\nSigned-off-by: Florian Fainelli <f.fainelli@gmail.com>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/e6cc3be552f9fedf5fa6b37c285d7d27ffc08b03"},{"sha":"ccc7d5a1cdae78ccd623540dc87e281135a1c053","author":{"email":"1c24ea00d8ce704dffa3997c81be1310fc2bbac6@libc.org","name":"Rich Felker"},"message":"sh: fix function signature of cpu_coregroup_mask to match pointer type\n\nThe signedness mismatch of the argument type produces an error\ncompiling kernel/sched/core.c with -Werror=incompatible-pointer-types,\nwhich is now used by default.\n\nFixes: ea8daa7b9784 \"kbuild: Add option to turn incompatible pointer check into error\"\nSigned-off-by: Rich Felker <dalias@libc.org>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/ccc7d5a1cdae78ccd623540dc87e281135a1c053"},{"sha":"b30a337ca27c4f40439e4bfb290cba5f88d73bb7","author":{"email":"8d0fc11caeb4659419f0ba3104eb4a9d30848d42@canonical.com","name":"Ming Lei"},"message":"block: partition: initialize percpuref before sending out KOBJ_ADD\n\nThe initialization of partition's percpu_ref should have been done before\nsending out KOBJ_ADD uevent, which may cause userspace to read partition\ntable. So the uninitialized percpu_ref may be accessed in data path.\n\nThis patch fixes this issue reported by Naveen.\n\nReported-by: Naveen Kaje <nkaje@codeaurora.org>\nTested-by: Naveen Kaje <nkaje@codeaurora.org>\nFixes: 6c71013ecb7e2(block: partition: convert percpu ref)\nCc: <stable@vger.kernel.org> # v4.3+\nSigned-off-by: Ming Lei <ming.lei@canonical.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/b30a337ca27c4f40439e4bfb290cba5f88d73bb7"},{"sha":"77644ad86abd205742937010fa1cf4795e927212","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"bus: mvebu-mbus: use %pa to print phys_addr_t\n\nA recent change to the mbus driver added a warning printk that\nprints a phys_addr_t using the %x format string, which fails in\ncase we build with 64-bit phys_addr_t:\n\ndrivers/bus/mvebu-mbus.c: In function 'mvebu_mbus_get_dram_win_info':\ndrivers/bus/mvebu-mbus.c:975:9: error: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'phys_addr_t {aka long long unsigned int}' [-Werror=format=]\n\nThis uses the special %pa format string instead, so we always\nprint the correct type.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nFixes: f2900acea801 (\"bus: mvebu-mbus: provide api for obtaining IO and DRAM window information\")\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/77644ad86abd205742937010fa1cf4795e927212"},{"sha":"199831c77c50e6913e893b6bc268ba9f4a9a2bf8","author":{"email":"cbb7353e6d953ef360baf960c122346276c6e320@puiterwijk.org","name":"Patrick Uiterwijk"},"message":"ARM: mvebu: Correct unit address for linksys\n\nThe USB2 port for Armada 38x is defined to be at 58000, not at\n50000.\n\nCc: <stable@vger.kernel.org>\nFixes: 2d0a7addbd10 (\"ARM: Kirkwood: Add support for many Synology NAS devices\")\nSigned-off-by: Patrick Uiterwijk <patrick@puiterwijk.org>\nAcked-by: Imre Kaloz <kaloz@openwrt.org>\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/199831c77c50e6913e893b6bc268ba9f4a9a2bf8"},{"sha":"1809de7e7d37c585e01a1bcc583ea92b78fc759d","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@atomide.com","name":"Tony Lindgren"},"message":"Merge tag 'for-v4.6-rc/omap-fixes-a' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v4.6/fixes\n\nARM: OMAP2+: first hwmod fix for v4.6-rc\n\nFix a longstanding bug in the hwmod code that could cause\nhardware SYSCONFIG register values to not match the kernel's\nidea of what they should be, and that could result in lower\nperformance during IP block idle entry.\n\nBasic build, boot, and PM test logs are available here:\n\nhttp://www.pwsan.com/omap/testlogs/omap-hwmod-fixes-a-for-v4.6-rc/20160326231727/","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/1809de7e7d37c585e01a1bcc583ea92b78fc759d"},{"sha":"b60e1157d8faa7a44556fcda2d4f06e71e839fd3","author":{"email":"69088b01848c9e171296e8a6c10279802a3a8a84@endlessm.com","name":"Carlo Caione"},"message":"ARM: dts: amlogic: Split pinctrl device for Meson8 / Meson8b\n\nSigned-off-by: Carlo Caione <carlo@endlessm.com>\nReviewed-by: Andreas Färber <afaerber@suse.de>\nTested-by: Kevin Hilman <khilman@baylibre.com>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/b60e1157d8faa7a44556fcda2d4f06e71e839fd3"},{"sha":"11ca873574c2314de9f0cf1adf8b3be88e4e19ae","author":{"email":"69088b01848c9e171296e8a6c10279802a3a8a84@endlessm.com","name":"Carlo Caione"},"message":"documentation: Fix pinctrl documentation for Meson8 / Meson8b\n\nFix pin controller documentation introducing the new compatibles for\nthe pinctrl drivers specific for aobus / cbus.\n\nThis is needed because we have changed the pin controller driver: we\nhave now a single specialized pinctrl driver / compatible for each bus\nthe controller is attached to, instead of one single driver dealing with\nall the controllers we have on different buses.\n\nSigned-off-by: Carlo Caione <carlo@endlessm.com>\nAcked-by: Rob Herring <robh@kernel.org>","distinct":false,"url":"https://api.github.com/repos/OpenPhoenux/gta04-kernel/commits/11ca873574c2314de9f0cf1adf8b3be88e4e19ae"}]}