{"push_id":573691358,"size":11,"distinct_size":11,"ref":"refs/heads/lp5.0-test","head":"f16e117c39f3f99afc209e50ead08384ae68e726","before":"10194471d0c3a3142c0d777894fe2e18e496bcfb","commits":[{"sha":"6d9271e69c5469d9864a38e832315c7ead7c35e0","author":{"email":"c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","name":"Paul Reioux"},"message":"msm8974pro: regulator: adjust GFX regulator parameters\n\n* settings based on qcom documentation\n\nChange-Id: I57c0e3ad4ac40305d07e2095688fca1244398570\nSigned-off-by: Paul Reioux <reioux@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/6d9271e69c5469d9864a38e832315c7ead7c35e0"},{"sha":"00da49108066b48630767d93e98c0f5027912d12","author":{"email":"7bea83a20351847b48daf43f39cc78e40e8253bc@motorola.com","name":"Guojian Chen"},"message":"cpuidle: remove cross-cpu IPI by new latency request.\n\nwhen drivers request new latency requirement, it's not necessary to\nimmediately wake up another cpu by sending cross-cpu IPI, we can consider\nthe new latency to be taken into effect after next wakeup from idle,\nthis can save the unnecessary wakeup cost, and reduce the risk that\ndrivers may request latency in irq disabled context.\n\n[<c08e0cc0>] (__irq_svc+0x40/0x70) from [<c00e801c>] (smp_call_function_single+0x16c/0x240)\n[<c00e801c>] (smp_call_function_single+0x16c/0x240) from [<c00e855c>] (smp_call_function+0x40/0x6c)\n[<c00e855c>] (smp_call_function+0x40/0x6c) from [<c0601c9c>] (cpuidle_latency_notify+0x18/0x20)\n[<c0601c9c>] (cpuidle_latency_notify+0x18/0x20) from [<c00b7c28>] (blocking_notifier_call_chain+0x74/0x94)\n[<c00b7c28>] (blocking_notifier_call_chain+0x74/0x94) from [<c00d563c>] (pm_qos_update_target+0xe0/0x128)\n[<c00d563c>] (pm_qos_update_target+0xe0/0x128) from [<c0620d3c>] (msmsdcc_enable+0xac/0x158)\n[<c0620d3c>] (msmsdcc_enable+0xac/0x158) from [<c06050e0>] (mmc_try_claim_host+0xb0/0xb8)\n[<c06050e0>] (mmc_try_claim_host+0xb0/0xb8) from [<c0605318>] (mmc_start_bkops.part.15+0x50/0x2f4)\n[<c0605318>] (mmc_start_bkops.part.15+0x50/0x2f4) from [<c00ab768>] (process_one_work+0x124/0x55c)\n[<c00ab768>] (process_one_work+0x124/0x55c) from [<c00abfc8>] (worker_thread+0x178/0x45c)\n[<c00abfc8>] (worker_thread+0x178/0x45c) from [<c00b0b24>] (kthread+0x84/0x90)\n[<c00b0b24>] (kthread+0x84/0x90) from [<c000fdd4>] (kernel_thread_exit+0x0/0x8)\nDisabling lock debugging due to kernel taint\ncoresight-etb coresight-etb.0: ETB aborted\nKernel panic - not syncing: softlockup: hung tasks\n\nSigned-off-by: Guojian Chen <a21757@motorola.com>\nReviewed-on: http://gerrit.pcs.mot.com/532702\nSLT-Approved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Klocwork kwcheck <klocwork-kwcheck@sourceforge.mot.com>\nReviewed-by: Christopher Fries <qcf001@motorola.com>\nReviewed-by: David Ding <dding@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/00da49108066b48630767d93e98c0f5027912d12"},{"sha":"467d8d8dc6d1af9e435e0ffe233dfdcff3fb2ffd","author":{"email":"d9c384f6b6e27869ff3b53bd225c29030ac4166b@gmail.com","name":"Sergey Senozhatsky"},"message":"cpuidle: remove unused hrtimer_peek_ahead_timers() call\n\n  Author: Arjan van de Ven <arjan@linux.intel.com>\n  Date:   Sun Nov 9 12:45:10 2008 -0800\n\n     regression: disable timer peek-ahead for 2.6.28\n\n     It's showing up as regressions; disabling it very likely just papers\n     over an underlying issue, but time is running out for 2.6.28, lets get\n     back to this for 2.6.29\n\n Many years has passed since 2008, so it seems ok to remove whole `#if 0' block.\n\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Kevin Hilman <khilman@ti.com>\nCc: Trinabh Gupta <g.trinabh@gmail.com>\nCc: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>\nCc: Arjan van de Ven <arjan@infradead.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Len Brown <len.brown@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/467d8d8dc6d1af9e435e0ffe233dfdcff3fb2ffd"},{"sha":"ea106e774f3ef3b195c3f2dffeb3295f634a83a0","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"cpuidle: add checks to avoid NULL pointer dereference\n\nThe existing check for dev == NULL in __cpuidle_register_device() is\nrendered useless because dev is dereferenced before the check itself.\nMoreover, correctly speaking, it is the job of the callers of this\nfunction, i.e., cpuidle_register_device() & cpuidle_enable_device() (which\nalso happen to be exported functions) to ensure that\n__cpuidle_register_device() is called with a non-NULL dev.\n\nSo add the necessary dev == NULL checks in the two callers and remove the\n(useless) check from __cpuidle_register_device().\n\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nAcked-by: Daniel Lezcano <daniel.lezcano@linaro.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Len Brown <len.brown@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/ea106e774f3ef3b195c3f2dffeb3295f634a83a0"},{"sha":"c78068a9456b4a64ab7bc24408d0f9c378f45731","author":{"email":"df7da900ca6d4d8dc52d8adb26aa75aef11ea28b@intel.com","name":"ShuoX Liu"},"message":"cpuidle: move field disable from per-driver to per-cpu\n\nAndrew J.Schorr raises a question.  When he changes the disable setting on\na single CPU, it affects all the other CPUs.  Basically, currently, the\ndisable field is per-driver instead of per-cpu.  All the C states of the\nsame driver are shared by all CPU in the same machine.\n\nThe patch changes the `disable' field to per-cpu, so we could set this\nseparately for each cpu.\n\nSigned-off-by: ShuoX Liu <shuox.liu@intel.com>\nReported-by: Andrew J.Schorr <aschorr@telemetry-investments.com>\nReviewed-by: Yanmin Zhang <yanmin_zhang@intel.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Rafael J. Wysocki <rjw@sisk.pl>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/c78068a9456b4a64ab7bc24408d0f9c378f45731"},{"sha":"9aa000600685916eff9d6c99e4535115d4ceec48","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"ACPI idle, CPU hotplug: Fix NULL pointer dereference during hotplug\n\nOn a KVM guest, when a CPU is taken offline and brought back online, we hit\nthe following NULL pointer dereference:\n\n[   45.400843] Unregister pv shared memory for cpu 1\n[   45.412331] smpboot: CPU 1 is now offline\n[   45.529894] SMP alternatives: lockdep: fixing up alternatives\n[   45.533472] smpboot: Booting Node 0 Processor 1 APIC 0x1\n[   45.411526] kvm-clock: cpu 1, msr 0:7d14601, secondary cpu clock\n[   45.571370] KVM setup async PF for cpu 1\n[   45.572331] kvm-stealtime: cpu 1, msr 7d0e040\n[   45.575031] BUG: unable to handle kernel NULL pointer dereference at           (null)\n[   45.576017] IP: [<ffffffff81519f98>] cpuidle_disable_device+0x18/0x80\n[   45.576017] PGD 5dfb067 PUD 5da8067 PMD 0\n[   45.576017] Oops: 0000 [#1] SMP\n[   45.576017] Modules linked in:\n[   45.576017] CPU 0\n[   45.576017] Pid: 607, comm: stress_cpu_hotp Not tainted 3.6.0-padata-tp-debug #3 Bochs Bochs\n[   45.576017] RIP: 0010:[<ffffffff81519f98>]  [<ffffffff81519f98>] cpuidle_disable_device+0x18/0x80\n[   45.576017] RSP: 0018:ffff880005d93ce8  EFLAGS: 00010286\n[   45.576017] RAX: ffff880005d93fd8 RBX: 0000000000000000 RCX: 0000000000000006\n[   45.576017] RDX: 0000000000000006 RSI: 2222222222222222 RDI: 0000000000000000\n[   45.576017] RBP: ffff880005d93cf8 R08: 2222222222222222 R09: 2222222222222222\n[   45.576017] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n[   45.576017] R13: 0000000000000000 R14: ffffffff81c8cca0 R15: 0000000000000001\n[   45.576017] FS:  00007f91936ae700(0000) GS:ffff880007c00000(0000) knlGS:0000000000000000\n[   45.576017] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b\n[   45.576017] CR2: 0000000000000000 CR3: 0000000005db3000 CR4: 00000000000006f0\n[   45.576017] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[   45.576017] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n[   45.576017] Process stress_cpu_hotp (pid: 607, threadinfo ffff880005d92000, task ffff8800066bbf40)\n[   45.576017] Stack:\n[   45.576017]  ffff880007a96400 0000000000000000 ffff880005d93d28 ffffffff813ac689\n[   45.576017]  ffff880007a96400 ffff880007a96400 0000000000000002 ffffffff81cd8d01\n[   45.576017]  ffff880005d93d58 ffffffff813aa498 0000000000000001 00000000ffffffdd\n[   45.576017] Call Trace:\n[   45.576017]  [<ffffffff813ac689>] acpi_processor_hotplug+0x55/0x97\n[   45.576017]  [<ffffffff813aa498>] acpi_cpu_soft_notify+0x93/0xce\n[   45.576017]  [<ffffffff816ae47d>] notifier_call_chain+0x5d/0x110\n[   45.576017]  [<ffffffff8109730e>] __raw_notifier_call_chain+0xe/0x10\n[   45.576017]  [<ffffffff81069050>] __cpu_notify+0x20/0x40\n[   45.576017]  [<ffffffff81069085>] cpu_notify+0x15/0x20\n[   45.576017]  [<ffffffff816978f1>] _cpu_up+0xee/0x137\n[   45.576017]  [<ffffffff81697983>] cpu_up+0x49/0x59\n[   45.576017]  [<ffffffff8168758d>] store_online+0x9d/0xe0\n[   45.576017]  [<ffffffff8140a9f8>] dev_attr_store+0x18/0x30\n[   45.576017]  [<ffffffff812322c0>] sysfs_write_file+0xe0/0x150\n[   45.576017]  [<ffffffff811b389c>] vfs_write+0xac/0x180\n[   45.576017]  [<ffffffff811b3be2>] sys_write+0x52/0xa0\n[   45.576017]  [<ffffffff816b31e9>] system_call_fastpath+0x16/0x1b\n[   45.576017] Code: 48 c7 c7 40 e5 ca 81 e8 07 d0 18 00 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 48 83 ec 10 48 89 5d f0 4c 89 65 f8 48 89 fb <f6> 07 02 75 13 48 8b 5d f0 4c 8b 65 f8 c9 c3 66 0f 1f 84 00 00\n[   45.576017] RIP  [<ffffffff81519f98>] cpuidle_disable_device+0x18/0x80\n[   45.576017]  RSP <ffff880005d93ce8>\n[   45.576017] CR2: 0000000000000000\n[   45.656079] ---[ end trace 433d6c9ac0b02cef ]---\n\nAnalysis:\nCommit 3d339dc (cpuidle / ACPI : move cpuidle_device field out of the\nacpi_processor_power structure()) made the allocation of the dev structure\n(struct cpuidle) of a CPU dynamic, whereas previously it was statically\nallocated. And this dynamic allocation occurs in acpi_processor_power_init()\nif pr->flags.power evaluates to non-zero.\n\nOn KVM guests, pr->flags.power evaluates to zero, hence dev is never\nallocated. This causes the NULL pointer (dev) dereference in\ncpuidle_disable_device() during a subsequent CPU online operation. Fix this\nby ensuring that dev is non-NULL before dereferencing.\n\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nSigned-off-by: Len Brown <len.brown@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Chet Kener <Cl3Kener@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/9aa000600685916eff9d6c99e4535115d4ceec48"},{"sha":"53d5aa5bc1d3178820dfbc733451870c07909111","author":{"email":"5db23874f34e45d59c69d81cd72d048d558566d7@gmail.com","name":"anarkia1976"},"message":"arm: dts: msm8974pro: Allow power collapse as minimum l2 gdhs mode","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/53d5aa5bc1d3178820dfbc733451870c07909111"},{"sha":"c767e4e780134a05b5099f9e1b3ef14b1759fde8","author":{"email":"5db23874f34e45d59c69d81cd72d048d558566d7@gmail.com","name":"anarkia1976"},"message":"cpufreq: cpu-boost: enable at boot\n\nSigned-off-by: martinusbe <martinusbe@gmail.com>\n\nConflicts:\n\tdrivers/cpufreq/cpu-boost.c\n\nChange-Id: I477d89d6810e52d163501da5a6a8185c67715368","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/c767e4e780134a05b5099f9e1b3ef14b1759fde8"},{"sha":"56b5929eab4d36ab386e9e2eda715fddc0c93a46","author":{"email":"5db23874f34e45d59c69d81cd72d048d558566d7@gmail.com","name":"anarkia1976"},"message":"xz: Optimize Sfck Compression","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/56b5929eab4d36ab386e9e2eda715fddc0c93a46"},{"sha":"77973fe1a9614549b957c1ebfba899ae3be279aa","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"msm: thermal: fix init with msm_thermal\n\n * not using ioctl interface for this in-kernel solution\nso prevent msm_thermal-dev to be built\n * use higher frequency points than my N5 driver because\nBacon rarely gets really hot so we don't need to throttle\nas heavy\n * re-structure init->register<->exit flow compared to the\nN5 code. We don't rely on board init call anymore. Besides\nexterns are fugly. The rest is on the msm_thermal merge side\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tarch/arm/mach-msm/oppo/board-8974-oppo.c","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/77973fe1a9614549b957c1ebfba899ae3be279aa"},{"sha":"f16e117c39f3f99afc209e50ead08384ae68e726","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"wlan: just shut up...\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Validus-Kernel/android_kernel_oneplus_msm8974/commits/f16e117c39f3f99afc209e50ead08384ae68e726"}]}