{"push_id":1217658528,"size":6,"distinct_size":6,"ref":"refs/heads/m6","head":"5eec157eee0aef89dfc55d761f2979c58ec563bf","before":"13f872cfb01996e72b9918241287f8728c2b85be","commits":[{"sha":"a80f41dab0ec1474a881ce56bd3388d7ec105464","author":{"name":"Rashed Abdel-Tawab","email":"feca779290058b319cc846b6d771969ec255fa0f@linux.com"},"message":"bcmdhd: Restore default wakelocks and timing\n\nThis is a combination of 2 commits.\nThe first commit's message is:\n\nRevert \"bcmdhd: Decrease to 250 ms\"\n\nThis reverts commit bd551cc00c417970519dd486f0533c98e45be2a8.\n\nThis is the 2nd commit message:\n\nRevert \"bcmdhd: reduce wakelocks\"\n\nThis reverts commit cbce1c3debcf404b4e5f741a1d5d2d8b9e83435c.\n\nChange-Id: Idf213d67dc8bbf9bca94591a9c8977f96a92109a","distinct":true,"url":"https://api.github.com/repos/StuntRR/StuntRR-kernel/commits/a80f41dab0ec1474a881ce56bd3388d7ec105464"},{"sha":"5c02495df153fd1a6a759acf9cbae192112629cb","author":{"name":"Ruchi Kandoi","email":"1d1bb2ca737b8740d7a99166510e781fa0bc7c0b@google.com"},"message":"nf: IDLETIMER: Adds the uid field in the msg\n\nMessage notifications contains an additional uid field. This field\nrepresents the uid that was responsible for waking the radio. And hence\nit is present only in notifications stating that the radio is now\nactive.\n\nChange-Id: I18fc73eada512e370d7ab24fc9f890845037b729\nSigned-off-by: Ruchi Kandoi <kandoiruchi@google.com>\nBug: 20264396","distinct":true,"url":"https://api.github.com/repos/StuntRR/StuntRR-kernel/commits/5c02495df153fd1a6a759acf9cbae192112629cb"},{"sha":"1ba8b643ad313279a31c1847d5d633b45ce273ae","author":{"name":"Greg Kroah-Hartman","email":"4931344b09d7a7d3573e8b1ebec918e229ead9bf@google.com"},"message":"arm: configs: g2: Disable CONFIG_PFT as it is unsupported\n\nDisable the drivers/platform/msm/pft.c driver as it is unsupported by\nQualcomm, and opens us up to a wide range of potential attack surfaces\nthat has not been audited by anyone.\n\nQualcomm recommends that it be disabled, as it hooks into SELinux in\nsome \"interesting\" ways, and the userspace portion of the code is not\neven part of the image.\n\nBug: 28588434\nChange-Id: I7fb1258839db984b34074bb53a0174d63393d728\nQualcomm-case-number: 02440206","distinct":true,"url":"https://api.github.com/repos/StuntRR/StuntRR-kernel/commits/1ba8b643ad313279a31c1847d5d633b45ce273ae"},{"sha":"9b1cb880ae5ab151abd19ae583d47d4607158d5d","author":{"name":"Kumar Gala","email":"0d3a1b29a2623bb798be1fa3928fec51a4eb84f0@codeaurora.org"},"message":"msm: reorder init calls in board's init_machine handler\n\nThere are a few minor ordering issues that cause us to have either extra\ncode in drivers or issues with doing proper memory mapping in drivers for\nregions of the memory map they use.\n\nWe should be populating the device structures from DT before we call any\nparticular driver init so that the drivers probe function can be called\nat the same time (with a proper platform device).\n\nAdditionally, we should be calling smem_init before socinfo_init as\nsocinfo utilizes smem.  (We have extra code in smem to handle calls before\nsmem_init/smem_probe are called that we could remove if we order init\ncalls properly).\n\nChange-Id: If616190f7310b7779e0ff1702bb0f873f4c5471d\nSigned-off-by: Kumar Gala <galak@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/StuntRR/StuntRR-kernel/commits/9b1cb880ae5ab151abd19ae583d47d4607158d5d"},{"sha":"67e91a08739988e7deb8d48adb9a4affac060443","author":{"name":"Amir Goldstein","email":"0b738364b8ca3a28da789d34dc90511d1baa1175@cellrox.com"},"message":"sysrq: Emergency Remount R/O in reverse order\n\nThis change fixes a problem where reboot on Android panics the kernel\nalmost every time when file systems are mounted over loop devices.\n\nAndroid reboot command does:\n- sync\n- echo u > /proc/sysrq-trigger\n- syscall_reboot\n\nThe problem is with sysrq emergency remount R/O trying to remount-ro\nin wrong order.\nsince /data is re-mounted ro before loop devices, loop device\nremount-ro fails to flush the journal and panics the kernel:\n\n  EXT4-fs (loop0): Remounting filesystem read-only\n  EXT4-fs (loop0): previous I/O error to superblock detected\n  loop: Write error at byte offset 0, length 4096.\n  Buffer I/O error on device loop0, logical block 0\n  lost page write due to I/O error on loop0\n  Kernel panic - not syncing: EXT4-fs panic from previous error\n\nThe fix is quite simple. In do_emergency_remount(), use\nlist_for_each_entry_reverse() on sb list instead of list_for_each_entry().\nIt makes a lot of sense to umount the file systems in reverse order in\nwhich they were added to sb list.\n\nChange-Id: I4370e39b5873bd16ade5d5f9ddb2704beb02a2bb\nSigned-off-by: Amir Goldstein <amir@cellrox.com>\nAcked-by: Oren Laadan <orenl@cellrox.com>","distinct":true,"url":"https://api.github.com/repos/StuntRR/StuntRR-kernel/commits/67e91a08739988e7deb8d48adb9a4affac060443"},{"sha":"5eec157eee0aef89dfc55d761f2979c58ec563bf","author":{"name":"StuntRR","email":"9b0192987c255133490a8616d0520c5a0f2fac87@gmail.com"},"message":"Merge branch 'cm-13.0' of https://github.com/CyanogenMod/android_kernel_lge_msm8974 into m6","distinct":true,"url":"https://api.github.com/repos/StuntRR/StuntRR-kernel/commits/5eec157eee0aef89dfc55d761f2979c58ec563bf"}]}
{"actor":{"display_login":"StuntRR"}}