{"push_id":814829094,"size":36,"distinct_size":36,"ref":"refs/heads/cm-12.1","head":"c31f3cc9f93c1b3ec4b4823f5c4c39a10fc51140","before":"7a3522f7fab30c22e457159d415732ca9d1c7c1d","commits":[{"sha":"2018a191c7c5247dad4278f73268ecfd98c74bf3","author":{"email":"7a64587131759e403f468755d5771ab9982be523@msn.com","name":"hurtsky"},"message":"dt2w/s2w: should return 0 if proximity not covered\n\n*port out changes from neobuddy changes\n\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/2018a191c7c5247dad4278f73268ecfd98c74bf3"},{"sha":"c5ed8147844dec92530f1bb299354f0baa800052","author":{"email":"7a64587131759e403f468755d5771ab9982be523@msn.com","name":"hurtsky"},"message":"Partially revert some recent changes for dt2w/s2w\n\n*Consume too much power during deep sleep\n\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/c5ed8147844dec92530f1bb299354f0baa800052"},{"sha":"17d7217daa6b4cc8495a1f924056abad7e5be252","author":{"email":"1aae5ab9541d66245293c8fc1b9880f5df073631@linaro.org","name":"Anton Vorontsov"},"message":"memcg: add memory.pressure_level events\n\nWith this patch userland applications that want to maintain the\ninteractivity/memory allocation cost can use the pressure level\nnotifications.  The levels are defined like this:\n\nThe \"low\" level means that the system is reclaiming memory for new\nallocations.  Monitoring this reclaiming activity might be useful for\nmaintaining cache level.  Upon notification, the program (typically\n\"Activity Manager\") might analyze vmstat and act in advance (i.e.\nprematurely shutdown unimportant services).\n\nThe \"medium\" level means that the system is experiencing medium memory\npressure, the system might be making swap, paging out active file\ncaches, etc.  Upon this event applications may decide to further analyze\nvmstat/zoneinfo/memcg or internal memory usage statistics and free any\nresources that can be easily reconstructed or re-read from a disk.\n\nThe \"critical\" level means that the system is actively thrashing, it is\nabout to out of memory (OOM) or even the in-kernel OOM killer is on its\nway to trigger.  Applications should do whatever they can to help the\nsystem.  It might be too late to consult with vmstat or any other\nstatistics, so it's advisable to take an immediate action.\n\nThe events are propagated upward until the event is handled, i.e.  the\nevents are not pass-through.  Here is what this means: for example you\nhave three cgroups: A->B->C.  Now you set up an event listener on\ncgroups A, B and C, and suppose group C experiences some pressure.  In\nthis situation, only group C will receive the notification, i.e.  groups\nA and B will not receive it.  This is done to avoid excessive\n\"broadcasting\" of messages, which disturbs the system and which is\nespecially bad if we are low on memory or thrashing.  So, organize the\ncgroups wisely, or propagate the events manually (or, ask us to\nimplement the pass-through events, explaining why would you need them.)\n\nPerformance wise, the memory pressure notifications feature itself is\nlightweight and does not require much of bookkeeping, in contrast to the\nrest of memcg features.  Unfortunately, as of current memcg\nimplementation, pages accounting is an inseparable part and cannot be\nturned off.  The good news is that there are some efforts[1] to improve\nthe situation; plus, implementing the same, fully API-compatible[2]\ninterface for CONFIG_CGROUP_MEM_RES_CTLR=n case (e.g.  embedded) is also\na viable option, so it will not require any changes on the userland\nside.\n\n[1] http://permalink.gmane.org/gmane.linux.kernel.cgroups/6291\n[2] http://lkml.org/lkml/2013/2/21/454\n\nChange-Id: Ib7b9f7986008d423b84152e2781d0402a560c95e\n[akpm@linux-foundation.org: coding-style fixes]\n[akpm@linux-foundation.org: fix CONFIG_CGROPUPS=n warnings]\nSigned-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>\nAcked-by: Kirill A. Shutemov <kirill@shutemov.name>\nAcked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: David Rientjes <rientjes@google.com>\nCc: Pekka Enberg <penberg@kernel.org>\nCc: Mel Gorman <mgorman@suse.de>\nCc: Glauber Costa <glommer@parallels.com>\nCc: Michal Hocko <mhocko@suse.cz>\nCc: Luiz Capitulino <lcapitulino@redhat.com>\nCc: Greg Thelen <gthelen@google.com>\nCc: Leonid Moiseichuk <leonid.moiseichuk@nokia.com>\nCc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>\nCc: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/17d7217daa6b4cc8495a1f924056abad7e5be252"},{"sha":"87fdee17e665d245134d1f105b51ce8dfec37252","author":{"email":"db18ceb40708dab5e9bcdbeb620f7eed18da08e5@codeaurora.org","name":"Vinayak Menon"},"message":"mm: vmpressure: allow in-kernel clients to subscribe for events\n\nCurrently, vmpressure is tied to memcg and its events are\navailable only to userspace clients. This patch removes\nthe dependency on CONFIG_MEMCG and adds a mechanism for\nin-kernel clients to subscribe for vmpressure events (in\nfact raw vmpressure values are delivered instead of vmpressure\nlevels, to provide clients more flexibility to take actions\non custom pressure levels which are not currently defined\nby vmpressure module).\n\nChange-Id: I38010f166546e8d7f12f5f355b5dbfd6ba04d587\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/87fdee17e665d245134d1f105b51ce8dfec37252"},{"sha":"d0dd28d1f590c5d3e34257129fd704b1fe0ee768","author":{"email":"e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","name":"Laura Abbott"},"message":"mm: Add notifier framework for showing memory\n\nThere are many drivers in the kernel which can hold on\nto lots of memory. It can be useful to dump out all those\ndrivers at key points in the kernel. Introduct a notifier\nframework for dumping this information. When the notifiers\nare called, drivers can dump out the state of any memory\nthey may be using.\n\nChange-Id: Ifb2946964bf5d072552dd56d8d6dfdd794af6d84\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/d0dd28d1f590c5d3e34257129fd704b1fe0ee768"},{"sha":"73b83bdeec06c44d120df2dd4aa1e80a6b3144f1","author":{"email":"db18ceb40708dab5e9bcdbeb620f7eed18da08e5@codeaurora.org","name":"Vinayak Menon"},"message":"lowmemorykiller: adapt to vmpressure\n\nThere were issues reported, where page cache thrashing was\nobserved because of LMK not killing tasks when required,\nresulting in sluggishness and higher app launch latency.\nLMK does not kill a task for the following reasons.\n1. The free and file pages are above the LMK thresholds\n2. LMK tries to pick task with an adj level corresponding\nto current thresholds, but fails to do so because of the\nabsence of tasks in that level.\nBut sometimes it is better to kill a lower adj task, than thrashing.\nAnd there are cases where the number of file pages are huge, though\nwe dont thrash, the reclaim process becomes time consuming, since\nLMK triggers will be delayed because of higher number of file\npages. Even in such cases, when reclaim path finds it difficult\nto reclaim pages, it is better to trigger lmk to free up some memory\nfaster.\n\nThe basic idea here is to make LMK more aggressive dynamically\nwhen such a thrashing scenario is detected.\n\nTo detect thrashing, this patch uses vmpressure events.\nThe values of vmpressure upon which an action has to be taken,\nwas derived empirically.\n\nThis patch also adds tracepoints to validate this feature,\nalmk_shrink and almk_vmpressure.\n\nTwo knobs are available for the user to tune adaptive lmk\nbehaviour.\n\n/sys/module/lowmemorykiller/parameters/adaptive_lmk - Write\n1 to enable the feature, 0 to disable. By default disabled.\n\n/sys/module/lowmemorykiller/parameters/vmpressure_file_min -\nThis parameter controls the behaviour of LMK when vmpressure\nis in the range of 90-94. Adaptive lmk triggers based on number file\npages wrt vmpressure_file_min, when vmpressure is in the range of\n90-94. Usually this is a pseudo minfree value, higher than the\nhighest configured value in minfree array.\n\nChange-Id: I1a08160c35d3e33bdfd1d2c789c288fc07d0f0d3\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/73b83bdeec06c44d120df2dd4aa1e80a6b3144f1"},{"sha":"87457082018d13e2fc468c5314111cd275f0f7f8","author":{"email":"db18ceb40708dab5e9bcdbeb620f7eed18da08e5@codeaurora.org","name":"Vinayak Menon"},"message":"mm: vmpressure: scale pressure based on reclaim context\n\nThe existing calculation of vmpressure takes into account only\nthe ratio of reclaimed to scanned pages, but not the time spent\nor the difficulty in reclaiming those pages. For e.g. when there\nare quite a number of file pages in the system, an allocation\nrequest can be satisfied by reclaiming the file pages alone. If\nsuch a reclaim is succesful, the vmpressure value will remain low\nirrespective of the time spent by the reclaim code to free up the\nfile pages. With a feature like lowmemorykiller, killing a task\ncan be faster than reclaiming the file pages alone. So if the\nvmpressure values reflect the reclaim difficulty level, clients\ncan make a decision based on that, for e.g. to kill a task early.\n\nThis patch monitors the number of pages scanned in the direct\nreclaim path and scales the vmpressure level according to that.\n\nChange-Id: I6e643d29a9a1aa0814309253a8b690ad86ec0b13\n\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/87457082018d13e2fc468c5314111cd275f0f7f8"},{"sha":"a13f22fd037c487db227612173a6ca4b97591b28","author":{"email":"db18ceb40708dab5e9bcdbeb620f7eed18da08e5@codeaurora.org","name":"Vinayak Menon"},"message":"mm: vmpressure: account allocstalls only on higher pressures\n\nAt present any vmpressure value is scaled up if the pages are\nreclaimed through direct reclaim. This can result in false\nvmpressure values. Consider a case where a device is booted up\nand most of the memory is occuppied by file pages. kswapd will\nmake sure that high watermark is maintained. Now when a sudden\nhuge allocation request comes in, the system will definitely\nhave to get into direct reclaims. The vmpressures can be very low,\nbut because of allocstall accounting logic even these low values\nwill be scaled to values nearing 100. This can resulting in\nunnecessary LMK kills for example.\n\nChange-Id: Idd7c6724264ac89f1f68f2e9d70a32390ffca3e5\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/a13f22fd037c487db227612173a6ca4b97591b28"},{"sha":"0472a6a87a7ca532233b6da4b70041ef2321e715","author":{"email":"db18ceb40708dab5e9bcdbeb620f7eed18da08e5@codeaurora.org","name":"Vinayak Menon"},"message":"lowmemorykiller: avoid false adaptive LMK triggers\n\nIn vmpressure notifier of LMK, shift_adj would have been set\nby a previous invocation of notifier, which is not followed by\na lowmem_shrink yet. Since vmpressure has improved, reset\nshift_adj to avoid false adaptive LMK trigger.\n\nChange-Id: I2d77103d7c8f4d8a66e4652cba78e619a7bcef9a\n\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: hurtsky <sabmar_com@msn.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/0472a6a87a7ca532233b6da4b70041ef2321e715"},{"sha":"b74ae8380923db632906867ad8fcbe43b7a5e604","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"ARM: move VFP init to an earlier boot stage\n\nIn order to use the NEON unit in the kernel, we should\ninitialize it a bit earlier in the boot process so NEON users\nthat like to do a quick benchmark at load time (like the\nxor_blocks or RAID-6 code) find the NEON/VFP unit already\nenabled.\n\nReplaced late_initcall() with core_initcall().\n\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nAcked-by: Nicolas Pitre <nico@linaro.org>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>\n\nConflicts:\n\tarch/arm/vfp/vfpmodule.c\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>\n\nConflicts:\n\tarch/arm/vfp/vfpmodule.c\n\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/b74ae8380923db632906867ad8fcbe43b7a5e604"},{"sha":"c50ac997bd2e6067baa41e279f262e8873438e05","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"ARM: add support for kernel mode NEON\n\nIn order to safely support the use of NEON instructions in\nkernel mode, some precautions need to be taken:\n- the userland context that may be present in the registers (even\n  if the NEON/VFP is currently disabled) must be stored under the\n  correct task (which may not be 'current' in the UP case),\n- to avoid having to keep track of additional vfpstates for the\n  kernel side, disallow the use of NEON in interrupt context\n  and run with preemption disabled,\n- after use, re-enable preemption and re-enable the lazy restore\n  machinery by disabling the NEON/VFP unit.\n\nThis patch adds the functions kernel_neon_begin() and\nkernel_neon_end() which take care of the above. It also adds\nthe Kconfig symbol KERNEL_MODE_NEON to enable it.\n\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nAcked-by: Nicolas Pitre <nico@linaro.org>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>\n\nConflicts:\n\tarch/arm/vfp/vfpmodule.c\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>\n\nConflicts:\n\tarch/arm/vfp/vfpmodule.c\n\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/c50ac997bd2e6067baa41e279f262e8873438e05"},{"sha":"95ec97dc2a33b939e4de6df8441c471eb4aa92aa","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"ARM: crypto: add NEON accelerated XOR implementation\n\nAdd a source file xor-neon.c (which is really just the reference\nC implementation passed through the GCC vectorizer) and hook it\nup to the XOR framework.\n\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nAcked-by: Nicolas Pitre <nico@linaro.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/95ec97dc2a33b939e4de6df8441c471eb4aa92aa"},{"sha":"c6aba9107e7efdf1fa46fc8f373b788b6e5c16e3","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"ARM: 7835/2: fix modular build of xor_blocks() with NEON enabled\n\nCommit 0195659 introduced a NEON accelerated version of the xor_blocks()\nfunction, but it needs the changes in this patch to allow it to be built\nas a module rather than statically into the kernel.\n\nThis patch creates a separate module xor-neon.ko which exports the NEON\ninner xor_blocks() functions depended upon by the regular xor.ko if it\nis built with CONFIG_KERNEL_MODE_NEON=y\n\nReported-by: Josh Boyer <jwboyer@fedoraproject.org>\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/c6aba9107e7efdf1fa46fc8f373b788b6e5c16e3"},{"sha":"0d1930331860f50096329c296b3cf9cfb271572f","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"arm: vfpmodule: Fix warning procfs vfp_bounce reporting failed\n\nCreation of procfs cpu/vfp_bounce fails because we're initialized too early. Fix\nthis by creating it on rootfs_initcall as before the NEON patches.\n\n<6>[    0.130770] VFP support v0.3: implementor 51 architecture 64 part 6f varia\nnt 2 rev 0\n<4>[    0.130795] ------------[ cut here ]------------\n<4>[    0.130813] WARNING: at fs/proc/generic.c:323 __xlate_proc_name+0xac/0xcc(\n)\n<4>[    0.130822] name 'cpu/vfp_bounce'\n<4>[    0.130855] [<c010e26c>] (unwind_backtrace+0x0/0x144) from [<c0a20f58>] (d\nump_stack+0x20/0x24)\n<4>[    0.130879] [<c0a20f58>] (dump_stack+0x20/0x24) from [<c019b670>] (warn_sl\nowpath_common+0x58/0x70)\n<4>[    0.130899] [<c019b670>] (warn_slowpath_common+0x58/0x70) from [<c019b704>\n] (warn_slowpath_fmt+0x40/0x48)\n<4>[    0.130919] [<c019b704>] (warn_slowpath_fmt+0x40/0x48) from [<c02c2ad8>] (\n__xlate_proc_name+0xac/0xcc)\n<4>[    0.130938] [<c02c2ad8>] (__xlate_proc_name+0xac/0xcc) from [<c02c2b50>] (\n__proc_create+0x58/0x100)\n<4>[    0.130956] [<c02c2b50>] (__proc_create+0x58/0x100) from [<c02c2ed0>] (pro\nc_create_data+0x5c/0xc0)\n<4>[    0.130979] [<c02c2ed0>] (proc_create_data+0x5c/0xc0) from [<c0f03484>] (v\nfp_init+0x19c/0x200)\n<4>[    0.131000] [<c0f03484>] (vfp_init+0x19c/0x200) from [<c0f00c98>] (do_one_\ninitcall+0x98/0x168)\n<4>[    0.131020] [<c0f00c98>] (do_one_initcall+0x98/0x168) from [<c0f00e60>] (k\nernel_init+0xf8/0x1b4)\n<4>[    0.131043] [<c0f00e60>] (kernel_init+0xf8/0x1b4) from [<c01081a0>] (kerne\nl_thread_exit+0x0/0x8)\n<4>[    0.131076] ---[ end trace ea6d9a9b5e947151 ]---\n<3>[    0.131086] Failed to create procfs node for VFP bounce reporting\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/0d1930331860f50096329c296b3cf9cfb271572f"},{"sha":"37b2611f6608d898a2dfaf4c575cedea99135266","author":{"email":"a0e0bc655fdc6685e623efd3336a27ce1c465fa0@hotmail.de","name":"Blechd0se"},"message":"vfp: remove double entries\n\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/37b2611f6608d898a2dfaf4c575cedea99135266"},{"sha":"539b0f718679406d20ca604839595b85ed657682","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"ARM: pull in <asm/simd.h> from asm-generic\n\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/539b0f718679406d20ca604839595b85ed657682"},{"sha":"595ea8473daa5ed02ba7d04988ba342e291de116","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"crypto: arm/aes update NEON AES module to latest OpenSSL version\n\nThis updates the bit sliced AES module to the latest version in the\nupstream OpenSSL repository (e620e5ae37bc). This is needed to fix a\nbug in the XTS decryption path, where data chunked in a certain way\ncould trigger the ciphertext stealing code, which is not supposed to\nbe active in the kernel build (The kernel implementation of XTS only\nsupports round multiples of the AES block size of 16 bytes, whereas\nthe conformant OpenSSL implementation of XTS supports inputs of\narbitrary size by applying ciphertext stealing). This is fixed in\nthe upstream version by adding the missing #ifndef XTS_CHAIN_TWEAK\naround the offending instructions.\n\nThe upstream code also contains the change applied by Russell to\nbuild the code unconditionally, i.e., even if __LINUX_ARM_ARCH__ < 7,\nbut implemented slightly differently.\n\nCc: stable@vger.kernel.org\nFixes: e4e7f10bfc40 (\"ARM: add support for bit sliced AES using NEON instructions\")\nReported-by: Adrian Kotelba <adrian.kotelba@gmail.com>\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nTested-by: Milan Broz <gmazyland@gmail.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\n\nChange-Id: I8973ae15cb082993c954b573bef9baa7195157e7","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/595ea8473daa5ed02ba7d04988ba342e291de116"},{"sha":"b8433dc333d4cb245410a27d94cc2f7d8a25c6fe","author":{"email":"78601e57ee83647e8b7edd75f0813a55a70302d1@gmail.com","name":"Dave Daynard"},"message":"mm: vmpressure: fix backport\n\nChange-Id: I26f4303038ccedff56211f2b11250760e5a84ad8","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/b8433dc333d4cb245410a27d94cc2f7d8a25c6fe"},{"sha":"0534d5904a7c49d19e64767658bb443f0fc6fbbe","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"msm: pm: Fix cpu collapse timeout\n\nLooks like caf mismerged. This may fix the following warning:\n\n<4>[  124.983957] ------------[ cut here ]------------\n<4>[  124.984381] WARNING: at arch/arm/mach-msm/msm-pm.c:837 msm_pm_wait_cpu_shu\ntdown+0x9c/0xb0()\n<4>[  124.984661] CPU2 didn't collapse in 2 ms\n<4>[  124.984869] [<c010e10c>] (unwind_backtrace+0x0/0x144) from [<c0a1c68c>] (d\nump_stack+0x20/0x24)\n<4>[  124.985170] [<c0a1c68c>] (dump_stack+0x20/0x24) from [<c019ab44>] (warn_sl\nowpath_common+0x58/0x70)\n<4>[  124.985464] [<c019ab44>] (warn_slowpath_common+0x58/0x70) from [<c019abd8>\n] (warn_slowpath_fmt+0x40/0x48)\n<4>[  124.985943] [<c019abd8>] (warn_slowpath_fmt+0x40/0x48) from [<c0179d30>] (\nmsm_pm_wait_cpu_shutdown+0x9c/0xb0)\n<4>[  124.986287] [<c0179d30>] (msm_pm_wait_cpu_shutdown+0x9c/0xb0) from [<c0126\n750>] (platform_cpu_kill+0x38/0x48)\n<4>[  124.986591] [<c0126750>] (platform_cpu_kill+0x38/0x48) from [<c010c6fc>] (\n__cpu_die+0x4c/0x98)\n<4>[  124.986778] [<c010c6fc>] (__cpu_die+0x4c/0x98) from [<c09ee9cc>] (_cpu_dow\nn+0xf8/0x2e0)\n<4>[  124.987074] [<c09ee9cc>] (_cpu_down+0xf8/0x2e0) from [<c09eec58>] (cpu_dow\nn+0x34/0x50)\n<4>[  124.987383] [<c09eec58>] (cpu_down+0x34/0x50) from [<c0194250>] (cpu_down_\nwork+0xc4/0xd8)\n<4>[  124.987564] [<c0194250>] (cpu_down_work+0xc4/0xd8) from [<c01b4e44>] (proc\ness_one_work+0x178/0x4f4)\n<4>[  124.987861] [<c01b4e44>] (process_one_work+0x178/0x4f4) from [<c01b5540>]\n(worker_thread+0x174/0x448)\n<4>[  124.988152] [<c01b5540>] (worker_thread+0x174/0x448) from [<c01bb8ac>] (kt\nhread+0xb4/0xc0)\n<4>[  124.988450] [<c01bb8ac>] (kthread+0xb4/0xc0) from [<c0108060>] (kernel_thr\nead_exit+0x0/0x8)\n<4>[  124.988725] ---[ end trace 77427e632785e345 ]---\n\nChange-Id: I40ea4459f333d44b3f1f11ebcec85466a896d974","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/0534d5904a7c49d19e64767658bb443f0fc6fbbe"},{"sha":"89f18a31e2d3ed7fb3965b2bb9f36ba542dde21e","author":{"email":"cd30a9e5fcc43d5f9341b3b7540d9b4c19d1f53b@gmail.com","name":"RolanDroid"},"message":"Updated defconfigs\n\nSigned-off-by: RolanDroid <rolandosimoncelli8@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RolanDroid/android_kernel_motorola_msm8226/commits/89f18a31e2d3ed7fb3965b2bb9f36ba542dde21e"}]}