{"push_id":873287545,"size":78,"distinct_size":78,"ref":"refs/heads/android-6.0","head":"44532f933978371c85f567d9c25c2989b00b2850","before":"3c6a1b49ab9c66cd9df6df5757ab5b0c63c78711","commits":[{"sha":"beff574cb8f529d748dc6dcb3bd509ca8505b44c","author":{"email":"c9d759b3104576ab5fdc2a821cc98ac497a86a4d@hotmail.com","name":"fermasia"},"message":"disable msple mpdecision by default","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/beff574cb8f529d748dc6dcb3bd509ca8505b44c"},{"sha":"2ac9ad02ed42e771e5a7b9e816cbada9d14b96df","author":{"email":"7d26b35203412f18a7dea4f8e1db1a75b1c5b706@semaphore.gr","name":"Stratos Karafotis"},"message":"cpufreq: Initial CPU utilization should be 0\n\nSigned-off-by: Stratos Karafotis <stratosk@semaphore.gr>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tdrivers/cpufreq/cpufreq.c","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/2ac9ad02ed42e771e5a7b9e816cbada9d14b96df"},{"sha":"bd5fc72851d72d8d1fbd8ab1d0e2c97eadc372ae","author":{"email":"b7088a9c70345a9ab94cacab3cc3888d0a7dc884@euromail.se","name":"Henrik Rydberg"},"message":"Input: Send events one packet at a time\n\nOn heavy event loads, such as a multitouch driver, the irqsoff latency\ncan be as high as 250 us.  By accumulating a frame worth of data\nbefore passing it on, the latency can be dramatically reduced.  As a\nside effect, the special EV_SYN handling can be removed, since the\nframe is now atomic.\n\nThis patch adds the events() handler callback and uses it if it\nexists. The latency is improved by 50 us even without the callback.\n\nChange-Id: Iebd9b1868ae6300a922a45b6d104e7c2b38e4cf5\nCc: Daniel Kurtz <djkurtz@chromium.org>\nTested-by: Benjamin Tissoires <benjamin.tissoires@enac.fr>\nTested-by: Ping Cheng <pingc@wacom.com>\nTested-by: Sedat Dilek <sedat.dilek@gmail.com>\nAcked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Henrik Rydberg <rydberg@euromail.se>\n\nInput: Improve the events-per-packet estimate\n\nThe events-per-packet estimate has so far been used by MT devices\nonly. This patch adjusts the packet buffer size to also accomodate the\nKEY and MSC events.  Keyboards normally send one or two keys at a\ntime. MT devices normally send a number of button keys along with the\nMT information.  The buffer size chosen here covers those cases, and\nmatches the default buffer size in evdev. Since the input estimate is\nnow preferred, remove the special input-mt estimate.\n\nReviewed-and-tested-by: Ping Cheng <pingc@wacom.com>\nTested-by: Benjamin Tissoires <benjamin.tissoires@enac.fr>\nAcked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Henrik Rydberg <rydberg@euromail.se>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/bd5fc72851d72d8d1fbd8ab1d0e2c97eadc372ae"},{"sha":"459318f77aabe8a8f9e45a1c4238bd09ee31f972","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"sound: add sound control to increase headphones, speaker and mic gain.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nsound: wcd9320: tidy up things a little bit. Only accept signed values from now on. The 'headset gain' will only be used to remove some gain noise, increasing it beyond 1 step above the default doesn't make a difference so rather just have it decrease the gain.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nsound: wcd9320: implement separate locks to prevent derps\n\n* playback, speaker and record locks only to the changed\nregister values, we don't need the locks to go through other\nregisters\n* this fixes a bug where a user adjusted the headphones gain\nand speaker and/or mic would stop working because the lock was\nenabled and the switch case would return earlier than it should\n* qualcomm, up yours\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tdrivers/misc/Makefile","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/459318f77aabe8a8f9e45a1c4238bd09ee31f972"},{"sha":"e2eb0c566e04b0cf4af6fedad5020913b147a723","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"arm: use -mtune=cortex-a15 for Krait targets\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/e2eb0c566e04b0cf4af6fedad5020913b147a723"},{"sha":"a1a3a04518ffbbb40bc9d5746e053430a3c094d3","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"arm: msm8974: enable Motorola's enhanced memory routines\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tarch/arm/mach-msm/Kconfig","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/a1a3a04518ffbbb40bc9d5746e053430a3c094d3"},{"sha":"263031b7dad4c6244090b4578b47c00a3a167240","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"power: make sync on suspend optional\npropagate from (CR).\n\nOn embedded devices with built-in batteries, it is not so\nimportant to sync the file systems before suspend.  The chance\nof losing power during suspend are no greater than they are\nwhen the system is awake.  The sync operations can greatly\nincrease suspend latency when the system has accrued many dirty\npages and/or the target storage devices are not particularly\nfast.\n\nThis commit adds a kernel config option to allow file system\nsync in the suspend path to be disabled.\n\nIt is enabled by default.\n\nChange-Id: Ib2ac24df861373d67e24f4ac3230ae4636e6c62f\nSigned-off-by: Russ Knize <Russ.Knize@motorola.com>\nSigned-off-by: Lianwei Wang <a22439@motorola.com>\nReviewed-on: http://gerrit.mot.com/692815\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Russell Knize <rknize@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>\nReviewed-by: Christopher Fries <cfries@motorola.com>\n[picked from goo.gl/MQbJYb]\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tkernel/power/suspend.c","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/263031b7dad4c6244090b4578b47c00a3a167240"},{"sha":"2e15bcc08032bf1b610a392b9d4afa43ffc5a318","author":{"email":"f2a4cf793007be8f81a774dc7806c1ffea7b4a2c@intel.com","name":"Zhang Rui"},"message":"PM: Introduce suspend state PM_SUSPEND_FREEZE\n\nPM_SUSPEND_FREEZE state is a general state that\ndoes not need any platform specific support, it equals\nfrozen processes + suspended devices + idle processors.\n\nCompared with PM_SUSPEND_MEMORY,\nPM_SUSPEND_FREEZE saves less power\nbecause the system is still in a running state.\nPM_SUSPEND_FREEZE has less resume latency because it does not\ntouch BIOS, and the processors are in idle state.\n\nCompared with RTPM/idle,\nPM_SUSPEND_FREEZE saves more power as\n1. the processor has longer sleep time because processes are frozen.\n   The deeper c-state the processor supports, more power saving we can get.\n2. PM_SUSPEND_FREEZE uses system suspend code path, thus we can get\n   more power saving from the devices that does not have good RTPM support.\n\nThis state is useful for\n1) platforms that do not have STR, or have a broken STR.\n2) platforms that have an extremely low power idle state,\n   which can be used to replace STR.\n\nThe following describes how PM_SUSPEND_FREEZE state works.\n1. echo freeze > /sys/power/state\n2. the processes are frozen.\n3. all the devices are suspended.\n4. all the processors are blocked by a wait queue\n5. all the processors idles and enters (Deep) c-state.\n6. an interrupt fires.\n7. a processor is woken up and handles the irq.\n8. if it is a general event,\n   a) the irq handler runs and quites.\n   b) goto step 4.\n9. if it is a real wake event, say, power button pressing, keyboard touch, mouse moving,\n   a) the irq handler runs and activate the wakeup source\n   b) wakeup_source_activate() notifies the wait queue.\n   c) system starts resuming from PM_SUSPEND_FREEZE\n10. all the devices are resumed.\n11. all the processes are unfrozen.\n12. system is back to working.\n\nKnown Issue:\nThe wakeup of this new PM_SUSPEND_FREEZE state may behave differently\nfrom the previous suspend state.\nTake ACPI platform for example, there are some GPEs that only enabled\nwhen the system is in sleep state, to wake the system backk from S3/S4.\nBut we are not touching these GPEs during transition to PM_SUSPEND_FREEZE.\nThis means we may lose some wake event.\nBut on the other hand, as we do not disable all the Interrupts during\nPM_SUSPEND_FREEZE, we may get some extra \"wakeup\" Interrupts, that are\nnot available for S3/S4.\n\nThe patches has been tested on an old Sony laptop, and here are the results:\n\nAverage Power:\n1. RPTM/idle for half an hour:\n   14.8W, 12.6W, 14.1W, 12.5W, 14.4W, 13.2W, 12.9W\n2. Freeze for half an hour:\n   11W, 10.4W, 9.4W, 11.3W 10.5W\n3. RTPM/idle for three hours:\n   11.6W\n4. Freeze for three hours:\n   10W\n5. Suspend to Memory:\n   0.5~0.9W\n\nAverage Resume Latency:\n1. RTPM/idle with a black screen: (From pressing keyboard to screen back)\n   Less than 0.2s\n2. Freeze: (From pressing power button to screen back)\n   2.50s\n3. Suspend to Memory: (From pressing power button to screen back)\n   4.33s\n\n>From the results, we can see that all the platforms should benefit from\nthis patch, even if it does not have Low Power S0.\n\nSigned-off-by: Zhang Rui <rui.zhang@intel.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tkernel/power/main.c\n\tkernel/power/suspend.c\n\nConflicts:\n\tkernel/power/suspend.c","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/2e15bcc08032bf1b610a392b9d4afa43ffc5a318"},{"sha":"5381f25a0d5e49ea7c9551fe849dd9e05d5d2e2c","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire. From http://ripke.com/loadavg/moire\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/5381f25a0d5e49ea7c9551fe849dd9e05d5d2e2c"},{"sha":"2855bc2d3d6c94ce338188ba6d4bd5f5a0d55bd3","author":{"email":"44dab0b659bc57509a0949ce7352600ac0beac12@motorola.com","name":"Joe Swantek"},"message":"power: quickwakeup: initial driver\n\nThis driver allows clients to register code to be called upon wakeup\nso that clients can perform specific checks and vote to drop the system\nback into suspend without fully resuming if the wake reason was a special\nquick wakeup event.\n\nPropagation of (CR)\n\nSigned-off-by: James Wylder <jwylder1@motorola.com>\nSigned-off-by: Jared Suttles <jsuttles@motorola.com>\nSigned-off-by: Joe Swantek <w98568@motorola.com>\nReviewed-on: http://gerrit.mot.com/648051\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Joseph Swantek <jswantek@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>\nReviewed-by: Patrick Auchter <auchter@motorola.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tkernel/power/Kconfig","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/2855bc2d3d6c94ce338188ba6d4bd5f5a0d55bd3"},{"sha":"5f55edda0b8609c9b2f48a28911bd1a2ea541239","author":{"email":"ed3b799f219469bc55cb495024ea5cafc3a57fb1@motorola.com","name":"Joe Swantek"},"message":"power: catch wake-up requests in suspend_again\n\nIt is possible during the processing of suspend_again() that a\nwake-up request (i.e. pm_stay_awake()) be made by a driver in response\nto an outside event (i.e. hw interrupt, etc.). Currently, when\nsuspend_again() requests to re-enter suspend, suspend_enter() runs\nto re-enter suspend. The pm_wakeup_pending() function is called to check\nfor any wake-up requests. However, this function is essentially disabled\nbecause the events_check_enabled flag is set to false by the previous\nrun through suspend_enter(). This causes any wake-up request made\nduring the processing of suspend_again() to be delayed until the next\ntime the kernel resumes sometime in the future.\n\nTo resolve this issue, if suspend_again() votes to re-enter\nsuspend_enter() the count of wake-up requests is re-evaluated\nand the events_check_enabled flag set correctly based on the\npresence of wake-up requests that occurred during suspend_again().\n\nSigned-off-by: Joe Swantek <jswantek@motorola.com>\nReviewed-by: Patrick Auchter <auchter@motorola.com>\nReviewed-by: Christopher Fries <cfries@motorola.com>\nSLTApproved: Christopher Fries <cfries@motorola.com>\nReviewed-by: Ravi Chebolu <arc095@motorola.com>\nReviewed-by: Fred Fettinger <fettinge@motorola.com>\nReviewed-by: Jeffrey Carlyle <jeff.carlyle@motorola.com>\nReviewed-by: Russell Knize <rknize@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/5f55edda0b8609c9b2f48a28911bd1a2ea541239"},{"sha":"59ae686c89a06407e711dc7782d48fbea77aed45","author":{"email":"44dab0b659bc57509a0949ce7352600ac0beac12@motorola.com","name":"Joe Swantek"},"message":"msm: lpm-levels: add suspend_again handler\n\nCall quickwakeup clients to enable us to perform very small amounts of\nprocessing and then to drop quickly back into suspend.\n\nPropagation of (CR)\n\nSigned-off-by: Jared Suttles <jsuttles@motorola.com>\nSigned-off-by: Joe Swantek <w98568@motorola.com>\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Patrick Auchter <auchter@motorola.com>\nReviewed-by: Joseph Swantek <jswantek@motorola.com>\nSubmit-Approved: Jason Hrycay <jason.hrycay@motorola.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/59ae686c89a06407e711dc7782d48fbea77aed45"},{"sha":"077abfa7dee1fc95add89937ee2592e22f48e4ff","author":{"email":"d81636f43b7fe9ea4ed34ac31193fc2f65850979@gmail.com","name":"Stuart Hayes"},"message":"hrtimer: Prevent all reprogramming if hang detected\n\ncommit 6c6c0d5a1c949d2e084706f9e5fb1fccc175b265 upstream.\n\nIf the last hrtimer interrupt detected a hang it sets hang_detected=1\nand programs the clock event device with a delay to let the system\nmake progress.\n\nIf hang_detected == 1, we prevent reprogramming of the clock event\ndevice in hrtimer_reprogram() but not in hrtimer_force_reprogram().\n\nThis can lead to the following situation:\n\nhrtimer_interrupt()\n   hang_detected = 1;\n   program ce device to Xms from now (hang delay)\n\nWe have two timers pending:\n   T1 expires 50ms from now\n   T2 expires 5s from now\n\nNow T1 gets canceled, which causes hrtimer_force_reprogram() to be\ninvoked, which in turn programs the clock event device to T2 (5\nseconds from now).\n\nAny hrtimer_start after that will not reprogram the hardware due to\nhang_detected still being set. So we effectivly block all timers until\nthe T2 event fires and cleans up the hang situation.\n\nAdd a check for hang_detected to hrtimer_force_reprogram() which\nprevents the reprogramming of the hang delay in the hardware\ntimer. The subsequent hrtimer_interrupt will resolve all outstanding\nissues.\n\n[ tglx: Rewrote subject and changelog and fixed up the comment in\n  \thrtimer_force_reprogram() ]\n\nSigned-off-by: Stuart Hayes <stuart.w.hayes@gmail.com>\nLink: http://lkml.kernel.org/r/53602DC6.2060101@gmail.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/077abfa7dee1fc95add89937ee2592e22f48e4ff"},{"sha":"06b867bdebd80d9cc47a421bae66ece019a727ca","author":{"email":"4066161ad7b49f5b39be02340a4a50c70c9a0caf@intel.com","name":"Leon Ma"},"message":"hrtimer: Prevent remote enqueue of leftmost timers\n\ncommit 012a45e3f4af68e86d85cce060c6c2fed56498b2 upstream.\n\nIf a cpu is idle and starts an hrtimer which is not pinned on that\nsame cpu, the nohz code might target the timer to a different cpu.\n\nIn the case that we switch the cpu base of the timer we already have a\nsanity check in place, which determines whether the timer is earlier\nthan the current leftmost timer on the target cpu. In that case we\nenqueue the timer on the current cpu because we cannot reprogram the\nclock event device on the target.\n\nIf the timers base is already the target CPU we do not have this\nsanity check in place so we enqueue the timer as the leftmost timer in\nthe target cpus rb tree, but we cannot reprogram the clock event\ndevice on the target cpu. So the timer expires late and subsequently\nprevents the reprogramming of the target cpu clock event device until\nthe previously programmed event fires or a timer with an earlier\nexpiry time gets enqueued on the target cpu itself.\n\nAdd the same target check as we have for the switch base case and\nstart the timer on the current cpu if it would become the leftmost\ntimer on the target.\n\n[ tglx: Rewrote subject and changelog ]\n\nSigned-off-by: Leon Ma <xindong.ma@intel.com>\nLink: http://lkml.kernel.org/r/1398847391-5994-1-git-send-email-xindong.ma@intel.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/06b867bdebd80d9cc47a421bae66ece019a727ca"},{"sha":"28675380ac519711552ba9214e2138f93ddad7ea","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"hrtimer: Set expiry time before switch_hrtimer_base()\n\ncommit 84ea7fe37908254c3bd90910921f6e1045c1747a upstream.\n\nswitch_hrtimer_base() calls hrtimer_check_target() which ensures that\nwe do not migrate a timer to a remote cpu if the timer expires before\nthe current programmed expiry time on that remote cpu.\n\nBut __hrtimer_start_range_ns() calls switch_hrtimer_base() before the\nnew expiry time is set. So the sanity check in hrtimer_check_target()\nis operating on stale or even uninitialized data.\n\nUpdate expiry time before calling switch_hrtimer_base().\n\n[ tglx: Rewrote changelog once again ]\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nCc: linaro-kernel@lists.linaro.org\nCc: linaro-networking@linaro.org\nCc: fweisbec@gmail.com\nCc: arvind.chauhan@arm.com\nLink: http://lkml.kernel.org/r/81999e148745fc51bbcd0615823fbab9b2e87e23.1399882253.git.viresh.kumar@linaro.org\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/28675380ac519711552ba9214e2138f93ddad7ea"},{"sha":"7a9785453433ea250e14ec0a87c425c534f31d12","author":{"email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de","name":"Thomas Gleixner"},"message":"futex: Prevent attaching to kernel threads\n\ncommit f0d71b3dcb8332f7971b5f2363632573e6d9486a upstream.\n\nWe happily allow userspace to declare a random kernel thread to be the\nowner of a user space PI futex.\n\nFound while analysing the fallout of Dave Jones syscall fuzzer.\n\nWe also should validate the thread group for private futexes and find\nsome fast way to validate whether the \"alleged\" owner has RW access on\nthe file which backs the SHM, but that's a separate issue.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Dave Jones <davej@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Darren Hart <darren@dvhart.com>\nCc: Davidlohr Bueso <davidlohr@hp.com>\nCc: Steven Rostedt <rostedt@goodmis.org>\nCc: Clark Williams <williams@redhat.com>\nCc: Paul McKenney <paulmck@linux.vnet.ibm.com>\nCc: Lai Jiangshan <laijs@cn.fujitsu.com>\nCc: Roland McGrath <roland@hack.frob.com>\nCc: Carlos ODonell <carlos@redhat.com>\nCc: Jakub Jelinek <jakub@redhat.com>\nCc: Michael Kerrisk <mtk.manpages@gmail.com>\nCc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>\nLink: http://lkml.kernel.org/r/20140512201701.194824402@linutronix.de\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/7a9785453433ea250e14ec0a87c425c534f31d12"},{"sha":"1adef127ae6b51e5d1f4ae2378c7afeba2e1fe57","author":{"email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de","name":"Thomas Gleixner"},"message":"futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == u…\n\n…addr2 in futex_requeue(..., requeue_pi=1)\n\nIf uaddr == uaddr2, then we have broken the rule of only requeueing from\na non-pi futex to a pi futex with this call.  If we attempt this, then\ndangling pointers may be left for rt_waiter resulting in an exploitable\ncondition.\n\nThis change brings futex_requeue() in line with futex_wait_requeue_pi()\nwhich performs the same check as per commit 6f7b0a2a5c0f (\"futex: Forbid\nuaddr == uaddr2 in futex_wait_requeue_pi()\")\n\n[ tglx: Compare the resulting keys as well, as uaddrs might be\n  \tdifferent depending on the mapping ]\n\nFixes CVE-2014-3153.\n\nChange-Id: I3d40911aca262eaefc3852327fa12bec416cd27d\nReported-by: Pinkie Pie\nSigned-off-by: Will Drewry <wad@chromium.org>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nCc: stable@vger.kernel.org\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nReviewed-by: Darren Hart <dvhart@linux.intel.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/1adef127ae6b51e5d1f4ae2378c7afeba2e1fe57"},{"sha":"7a18d6a9fbe4bbd0626a2daf0d7b7758856e3d2f","author":{"email":"c9d759b3104576ab5fdc2a821cc98ac497a86a4d@hotmail.com","name":"fermasia"},"message":"defconfig: add quickwakeup driver\n\nConflicts:\n\tarch/arm/configs/msm8974_find7op_defconfig","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/7a18d6a9fbe4bbd0626a2daf0d7b7758856e3d2f"},{"sha":"07c829bd9cedc330756357324d183b6dcea97952","author":{"email":"c9d759b3104576ab5fdc2a821cc98ac497a86a4d@hotmail.com","name":"fermasia"},"message":"Voltage Control: generic voltage control for DTS based kernels","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/07c829bd9cedc330756357324d183b6dcea97952"},{"sha":"d62e68b12013bd5e0bae10a36ff63ada3d6cdcc4","author":{"email":"c9d759b3104576ab5fdc2a821cc98ac497a86a4d@hotmail.com","name":"fermasia"},"message":"Voltage Control: Fix voltage setting bug\n\nConflicts:\n\tarch/arm/configs/msm8974_find7op_defconfig\n\nConflicts:\n\tarch/arm/configs/msm8974_find7op_defconfig","distinct":true,"url":"https://api.github.com/repos/kantjer/android_kernel_oppo_msm8974/commits/d62e68b12013bd5e0bae10a36ff63ada3d6cdcc4"}]}