{"push_id":732968445,"size":10,"distinct_size":10,"ref":"refs/heads/cm-12.1-caf","head":"70c1cc724f47f5dc0f8d046f1fe57ddbfc992359","before":"6c1bd8dab961003cc96d2cedbfdd02be5507d870","commits":[{"sha":"3dde8e6269834a89dd28c6e3cb855eadf7bda8e0","author":{"email":"dea94a0844b5eabbd4facc1feb96e20a0f3b79ea@googlemail.com","name":"Elektroschmock"},"message":"hammerhead: disable logger\n\nChange-Id: I547d2d418b5688764aeb0a2bb4731010e94b3bb7","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/3dde8e6269834a89dd28c6e3cb855eadf7bda8e0"},{"sha":"2e91932a013c8a2684ae4df79e8552db875a26ff","author":{"email":"dea94a0844b5eabbd4facc1feb96e20a0f3b79ea@googlemail.com","name":"Elektroschmock"},"message":"defconfig: turn off /dev/mem and /dev/kmem\n\nChange-Id: I1ee8f911bf946f6ad873ad56c85672b740d6aa4e","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/2e91932a013c8a2684ae4df79e8552db875a26ff"},{"sha":"c836378387b4b018516430f78466e209be3c3024","author":{"email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com","name":"Eric Dumazet"},"message":"rcu: Fix batch-limit size problem\n\ncommit 878d7439d0f45a95869e417576774673d1fa243f upstream.\n\nCommit 29c00b4a1d9e27 (rcu: Add event-tracing for RCU callback\ninvocation) added a regression in rcu_do_batch()\n\nUnder stress, RCU is supposed to allow to process all items in queue,\ninstead of a batch of 10 items (blimit), but an integer overflow makes\nthe effective limit being 1.  So, unless there is frequent idle periods\n(during which RCU ignores batch limits), RCU can be forced into a\nstate where it cannot keep up with the callback-generation rate,\neventually resulting in OOM.\n\nThis commit therefore converts a few variables in rcu_do_batch() from\nint to long to fix this problem, along with the module parameters\ncontrolling the batch limits.\n\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nConflicts:\n\tkernel/rcutree.c\n\nChange-Id: I07b1010d76df7b9ec76dd933b42d4106d0239e50","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/c836378387b4b018516430f78466e209be3c3024"},{"sha":"8f0bc07d81812654079a479a0f84e3009f1e900f","author":{"email":"a90a680fc254d136e5e0c1b07e0dfa8a9cd5d3cb@codeaurora.org","name":"Sunil Khatri"},"message":"msm: kgsl: Make global memory statistics atomic\n\nIf you run aggressive memory operations long enough, eventually you\nwill notice that the KGSL memory statistics will explode up into the\n3G range. This is a race condition on the statistics math which ends up\ngoing negative in certain cases.  Turning the statistics variables into\natomics should solve the problem once and for all. ONCE AND FOR ALL.\n\nChange-Id: Ic0dedbad61762d667550c22190c4f9d0b453829b\nSigned-off-by: Jordan Crouse <jcrouse@codeaurora.org>\nSigned-off-by: Sunil Khatri <sunilkh@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/8f0bc07d81812654079a479a0f84e3009f1e900f"},{"sha":"8000705e02c29cab96768996cc55378038edf582","author":{"email":"76e30dc6511df6537bc8f74ebde59f1a6034d162@codeaurora.org","name":"Vijayavardhan Vennapusa"},"message":"USB: dwc3: ep0: Use WARN_ON_ONCE to fix message flooding issue\n\nCurrently driver is using WARN_ON to print call stack whenever\nstarting control transfer fails. This could cause issue of\nflooding of messages. Hence fix this by moving to WARN_ON_ONCE.\nAlso add debug events in case of error instead printing error\nmessage.\n\nChange-Id: Ie3b52b046276d82a7055e9b43d081408c7bcff51\nSigned-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/8000705e02c29cab96768996cc55378038edf582"},{"sha":"831963af7d6092793859b4059167f2751f245080","author":{"email":"44e007e42f7a1553b8387cad56a79625b5879d5f@codeaurora.org","name":"Krishna Chaitanya Parimi"},"message":"msm: mdss: Minimize cases of BL lock in update backlight\n\nCalling backlight lock on every commit iteration was adding\noverhead. Altering the conditions to allow locking only for\ncase when unset backlight level is not zero.\n\nChange-Id: I023dccfa584cf641d042565b7ad2cb32c0724c55\nSigned-off-by: Krishna Chaitanya Parimi <cparimi@codeaurora.org>\nSigned-off-by: Nirmal Abraham <nabrah@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/831963af7d6092793859b4059167f2751f245080"},{"sha":"e61070db46004899c681c5656df6409eacd4b572","author":{"email":"76e30dc6511df6537bc8f74ebde59f1a6034d162@codeaurora.org","name":"Vijayavardhan Vennapusa"},"message":"USB: dwc3: msm: Don't disable/enable clocks if in lpm during block reset\n\nWhenever interrupt is triggered for erratic event, USB driver schedules\nwork to do USB block reset as part of recovery. Currently while doing\nblock reset, not checking whether USB is in lpm and going ahead with\ndisabling clocks which messup clock counters. Hence check if USB is in lpm\nand do disabling/enabling clocks only if it is not lpm.\n\nChange-Id: Ib28e76f0786184506bec69b7541e56dd7a16ed0f\nSigned-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/e61070db46004899c681c5656df6409eacd4b572"},{"sha":"bbbc07bdd43f83a168f251aece04b4cd6471a04b","author":{"email":"de8f51700df9f263ada91a596855b819cc525389@codeaurora.org","name":"Jessica Wagantall"},"message":"msm: ADSPRPC: Initialize hlist node pointers\n\nInitialize the hlist node with valid previous node pointer\nthat would allow for the node to be deleted in error scenarios\nwhere the buffer being passed from user space is invalid.\n\nChange-Id: Ib16ed9ad2b39ca616563a2e5315951461212de64\nSigned-off-by: Sathish Ambley <sathishambley@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/bbbc07bdd43f83a168f251aece04b4cd6471a04b"},{"sha":"b8933a9adc2a283906d2708c480268403665443f","author":{"email":"a6304dcc9634133b3aac1dadb9f15b6877f236d4@codeaurora.org","name":"Nirmal Abraham"},"message":"ARM: dts: msm: Limit ADSP CMA heap to lowmem for 8x26\n\nCommit 8360c416dc5bdabbfcc22a209eb9cc6c47be99ac (Remove fb\nmemory allocation) freed 8MB allocation from highmem which\nresulted in ADSP CMA heap being allocated in highmem instead\nof lowmem. This allocation along with other CMA heap allocations\nfrom highmem resulted in 'totalhigh_pages' to be calculated as\nzero at bootup and entire highmem being intialized with\nmigrate_type as MIGRATE_CMA for 8626. This lead to performance\ndegradation for some benchmark tests.\n\nTo resolve this, limit the ADSP CMA heap to lowmem so that the\n'totalhigh_pages' are not zero at bootup and not all highmem\nis initialized to MIGRATE_CMA.\n\nChange-Id: I55f49674696c81ee35944335d9d73d6f9fefa20c\nSigned-off-by: Nirmal Abraham <nabrah@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/b8933a9adc2a283906d2708c480268403665443f"},{"sha":"70c1cc724f47f5dc0f8d046f1fe57ddbfc992359","author":{"email":"563e52a359628987e3ec3a43d116ebecc87e39bc@codeaurora.org","name":"Balamurugan Alagarsamy"},"message":"msm: vidc: flush work handler before unloading firmware\n\nIn case if the spurious interrupts is handled, while the\npoweroff is done at the time of unloading firmware, can\ncreate crashes in iommu_attach_device. So, the\ncore work handler need to be flushed before doing\npower off and unloading the venus firmware.\n\nChange-Id: I6a9c5911da855c6d530fd4683a3d9ebebb45c1b0\nSigned-off-by: Balamurugan Alagarsamy <balaga@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/TeamBliss-Devices/android_kernel_lge_hammerhead/commits/70c1cc724f47f5dc0f8d046f1fe57ddbfc992359"}]}