{"push_id":1766193037,"size":51,"distinct_size":51,"ref":"refs/heads/test","head":"84e1d06796293ca873cb2a9a7347fe70219b127b","before":"ba35c615a3f41942ef2f8a98949d9bf8ddb4ab64","commits":[{"sha":"1002dcb0bb8c39d13ffa59925aa41ab9b75aed0d","author":{"name":"flar2","email":"54baee86d9719f38bf07b54ac189c5126488f211@gmail.com"},"message":"gitignore","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/1002dcb0bb8c39d13ffa59925aa41ab9b75aed0d"},{"sha":"d2dcdbea151a6f76baf0f8def54c9418a32cc73e","author":{"name":"flar2","email":"54baee86d9719f38bf07b54ac189c5126488f211@gmail.com"},"message":"Fix version name\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/d2dcdbea151a6f76baf0f8def54c9418a32cc73e"},{"sha":"cf7d02ff7b2a7a81905a46ae4e9dccb5c74b635c","author":{"name":"flar2","email":"54baee86d9719f38bf07b54ac189c5126488f211@gmail.com"},"message":"disable crc check\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/cf7d02ff7b2a7a81905a46ae4e9dccb5c74b635c"},{"sha":"408ce90c6922d5d9337e42bbe7b3bfe96c0cae44","author":{"name":"Jeff Liu","email":"7caaf2102f89e0af2e4ce8bfa65789b1f2f34247@oracle.com"},"message":"binfmt_elf.c: use get_random_int() to fix entropy depleting\n\nChanges:\n--------\nv4->v3:\n- s/random_stack_user()/get_atrandom_bytes()/\n- Move this function to ahead of its use to avoid the predeclaration.\n\nv3->v2:\n- Tweak code comments of random_stack_user().\n- Remove redundant bits mask and shift upon the random variable.\n\nv2->v1:\n- Fix random copy to check up buffer length that are not 4-byte multiples.\n\nv3 can be found at:\nhttp://www.spinics.net/lists/linux-fsdevel/msg59597.html\nv2 can be found at:\nhttp://www.spinics.net/lists/linux-fsdevel/msg59418.html\nv1 can be found at:\nhttp://www.spinics.net/lists/linux-fsdevel/msg59128.html\n\nThanks,\n-Jeff\n\nEntropy is quickly depleted under normal operations like ls(1), cat(1),\netc...  between 2.6.30 to current mainline, for instance:\n\n$ cat /proc/sys/kernel/random/entropy_avail\n3428\n$ cat /proc/sys/kernel/random/entropy_avail\n2911\n$cat /proc/sys/kernel/random/entropy_avail\n2620\n\nWe observed this problem has been occurring since 2.6.30 with\nfs/binfmt_elf.c: create_elf_tables()->get_random_bytes(), introduced by\nf06295b44c296c8f (\"ELF: implement AT_RANDOM for glibc PRNG seeding\").\n\n/*\n * Generate 16 random bytes for userspace PRNG seeding.\n */\nget_random_bytes(k_rand_bytes, sizeof(k_rand_bytes));\n\nThe patch introduces a wrapper around get_random_int() which has lower\noverhead than calling get_random_bytes() directly.\n\nWith this patch applied:\n$ cat /proc/sys/kernel/random/entropy_avail\n2731\n$ cat /proc/sys/kernel/random/entropy_avail\n2802\n$ cat /proc/sys/kernel/random/entropy_avail\n2878\n\nAnalyzed by John Sobecki.\n\nSigned-off-by: Jie Liu <jeff.liu@oracle.com>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: Andreas Dilger <aedilger@gmail.com>\nCc: Alan Cox <alan@linux.intel.com>\nCc: Arnd Bergmann <arnn@arndb.de>\nCc: John Sobecki <john.sobecki@oracle.com>\nCc: James Morris <james.l.morris@oracle.com>\nCc: Jakub Jelinek <jakub@redhat.com>\nCc: Ted Ts'o <tytso@mit.edu>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nCc: Kees Cook <keescook@chromium.org>\nCc: Ulrich Drepper <drepper@redhat.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/408ce90c6922d5d9337e42bbe7b3bfe96c0cae44"},{"sha":"3967c6cccefeefbc2b47d1b36e9af07c51a5eaaa","author":{"name":"Tim Murray","email":"1236fbd8e0651a86c12ed0f0b75aaeb5e5852ea8@google.com"},"message":"mmc: move to a SCHED_FIFO thread\n\nRunning mmcqd as a prio 120 thread forces it to compete with standard\nuser processes for IO performance, especially when the system is under\nsevere CPU load. Move it to a SCHED_FIFO thread to reduce the impact of\nload on IO performance.\n\nbug 25392275\n\nChange-Id: I1edfe73baa25e181367c30c1f40fee886e92b60d\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/3967c6cccefeefbc2b47d1b36e9af07c51a5eaaa"},{"sha":"a637f908b1d72cd3100356d62ebd704d87ba974a","author":{"name":"Neal Cardwell","email":"6eb0de8c52d8a3fcaae13b97cd10ce8592d0bd4f@google.com"},"message":"tcp: fix timing issue in CUBIC slope calculation\n\nThis patch fixes a bug in CUBIC that causes cwnd to increase slightly\ntoo slowly when multiple ACKs arrive in the same jiffy.\n\nIf cwnd is supposed to increase at a rate of more than once per jiffy,\nthen CUBIC was sometimes too slow. Because the bic_target is\ncalculated for a future point in time, calculated with time in\njiffies, the cwnd can increase over the course of the jiffy while the\nbic_target calculated as the proper CUBIC cwnd at time\nt=tcp_time_stamp+rtt does not increase, because tcp_time_stamp only\nincreases on jiffy tick boundaries.\n\nSo since the cnt is set to:\n\tca->cnt = cwnd / (bic_target - cwnd);\nas cwnd increases but bic_target does not increase due to jiffy\ngranularity, the cnt becomes too large, causing cwnd to increase\ntoo slowly.\n\nFor example:\n- suppose at the beginning of a jiffy, cwnd=40, bic_target=44\n- so CUBIC sets:\n   ca->cnt =  cwnd / (bic_target - cwnd) = 40 / (44 - 40) = 40/4 = 10\n- suppose we get 10 acks, each for 1 segment, so tcp_cong_avoid_ai()\n   increases cwnd to 41\n- so CUBIC sets:\n   ca->cnt =  cwnd / (bic_target - cwnd) = 41 / (44 - 41) = 41 / 3 = 13\n\nSo now CUBIC will wait for 13 packets to be ACKed before increasing\ncwnd to 42, insted of 10 as it should.\n\nThe fix is to avoid adjusting the slope (determined by ca->cnt)\nmultiple times within a jiffy, and instead skip to compute the Reno\ncwnd, the \"TCP friendliness\" code path.\n\nReported-by: Eyal Perry <eyalpe@mellanox.com>\nSigned-off-by: Neal Cardwell <ncardwell@google.com>\nSigned-off-by: Yuchung Cheng <ycheng@google.com>\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/a637f908b1d72cd3100356d62ebd704d87ba974a"},{"sha":"f8939ab1719d1ec6cf17de56f5c4d0feef161b24","author":{"name":"Mel Gorman","email":"7e4a4144b35252848d9a801e3e6fca62e0cbe9e6@suse.de"},"message":"mm: slub: Default slub_max_order to 0\n\nTo avoid locking and per-cpu overhead, SLUB optimisically uses\nhigh-order allocations up to order-3 by default and falls back to\nlower allocations if they fail. While care is taken that the caller\nand kswapd take no unusual steps in response to this, there are\nfurther consequences like shrinkers who have to free more objects to\nrelease any memory. There is anecdotal evidence that significant time\nis being spent looping in shrinkers with insufficient progress being\nmade (https://lkml.org/lkml/2011/4/28/361) and keeping kswapd awake.\n\nSLUB is now the default allocator and some bug reports have been\npinned down to SLUB using high orders during operations like\ncopying large amounts of data. SLUBs use of high-orders benefits\napplications that are sized to memory appropriately but this does not\nnecessarily apply to large file servers or desktops.  This patch\ncauses SLUB to use order-0 pages like SLAB does by default.\nThere is further evidence that this keeps kswapd's usage lower\n(https://lkml.org/lkml/2011/5/10/383).\n\nSigned-off-by: Mel Gorman <mgorman@suse.de>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/f8939ab1719d1ec6cf17de56f5c4d0feef161b24"},{"sha":"7d2a4b971d15d4b97aa95f8bdf6263ad23a25159","author":{"name":"flar2","email":"54baee86d9719f38bf07b54ac189c5126488f211@gmail.com"},"message":"AIO: Don't plug the I/O queue in do_io_submit()\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/7d2a4b971d15d4b97aa95f8bdf6263ad23a25159"},{"sha":"e90cede0fe38a82121e703d138304d026accbc0b","author":{"name":"Tahsin Erdogan","email":"f575aabfcf931cdd93bfc82db2c7bb41f58ee7dd@google.com"},"message":"block: Make CFQ default to IOPS mode on SSDs\n\nCFQ idling causes reduced IOPS throughput on non-rotational disks.\nSince disk head seeking is not applicable to SSDs, it doesn't really\nhelp performance by anticipating future near-by IO requests.\n\nBy turning off idling (and switching to IOPS mode), we allow other\nprocesses to dispatch IO requests down to the driver and so increase IO\nthroughput.\n\nFollowing FIO benchmark results were taken on a cloud SSD offering with\nidling on and off:\n\nIdling     iops    avg-lat(ms)    stddev            bw\n------------------------------------------------------\n    On     7054    90.107         38.697     28217KB/s\n   Off    29255    21.836         11.730    117022KB/s\n\nfio --name=temp --size=100G --time_based --ioengine=libaio \\\n    --randrepeat=0 --direct=1 --invalidate=1 --verify=0 \\\n    --verify_fatal=0 --rw=randread --blocksize=4k --group_reporting=1 \\\n    --filename=/dev/sdb --runtime=10 --iodepth=64 --numjobs=10\n\nAnd the following is from a local SSD run:\n\nIdling     iops    avg-lat(ms)    stddev            bw\n------------------------------------------------------\n    On    19320    33.043         14.068     77281KB/s\n   Off    21626    29.465         12.662     86507KB/s\n\nfio --name=temp --size=5G --time_based --ioengine=libaio \\\n    --randrepeat=0 --direct=1 --invalidate=1 --verify=0 \\\n    --verify_fatal=0 --rw=randread --blocksize=4k --group_reporting=1 \\\n    --filename=/fio_data --runtime=10 --iodepth=64 --numjobs=10\n\nChange-Id: I2311c1b349092d5d6afe5200037f6aeccf506e04\nReviewed-by: Nauman Rafique <nauman@google.com>\nSigned-off-by: Tahsin Erdogan <tahsin@google.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/e90cede0fe38a82121e703d138304d026accbc0b"},{"sha":"a8916ca1db6d994b38fd1569556e1b8654911ebf","author":{"name":"Namjae Jeon","email":"cee0fb13a02a9f6df517d42af792ebb078f2bc1f@samsung.com"},"message":"writeback: fix writeback cache thrashing\n\nConsider Process A: huge I/O on sda\n        doing heavy write operation - dirty memory becomes more\n        than dirty_background_ratio\n        on HDD - flusher thread flush-8:0\n\nConsider Process B: small I/O on sdb\n        doing while [1]; read 1024K + rewrite 1024K + sleep 2sec\n        on Flash device - flusher thread flush-8:16\n\nAs Process A is a heavy dirtier, dirty memory becomes more\nthan dirty_background_thresh. Due to this, below check becomes\ntrue(checking global_page_state in over_bground_thresh)\nfor all bdi devices(even for very small dirtied bdi - sdb):\n\nIn this case, even small cached data on 'sdb' is forced to flush\nand writeback cache thrashing happens.\n\nWhen we added debug prints inside above 'if' condition and ran\nabove Process A(heavy dirtier on bdi with flush-8:0) and\nProcess B(1024K frequent read/rewrite on bdi with flush-8:16)\nwe got below prints:\n\n[Test setup: ARM dual core CPU, 512 MB RAM]\n\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56064 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56704 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 84720 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 94720 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   384 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   960 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =    64 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92160 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   256 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   768 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =    64 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   256 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   320 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =     0 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92032 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 91968 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   192 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =  1024 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =    64 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   192 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   576 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =     0 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 84352 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   192 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   512 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =     0 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92608 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92544 KB\n\nAs mentioned in above log, when global dirty memory > global background_thresh\nsmall cached data is also forced to flush by flush-8:16.\nIf removing global background_thresh checking code, we can reduce cache\nthrashing of frequently used small data.\nAnd It will be great if we can reserve a portion of writeback cache using\nmin_ratio.\n\nAfter applying patch:\n$ echo 5 > /sys/block/sdb/bdi/min_ratio\n$ cat /sys/block/sdb/bdi/min_ratio\n5\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56064 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56704 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  84160 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  96960 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  94080 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93120 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93120 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  91520 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  89600 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93696 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93696 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  72960 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  90624 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  90624 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  90688 KB\n\nAs mentioned in the above logs, once cache is reserved for Process B,\nand patch is applied there is less writeback cache thrashing on sdb\nby frequent forced writeback by flush-8:16 in over_bground_thresh.\n\nAfter all, small cached data will be flushed by periodic writeback\nonce every dirty_writeback_interval.\n\nSuggested-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>\nSigned-off-by: Namjae Jeon <namjae.jeon@samsung.com>\nSigned-off-by: Vivek Trivedi <t.vivek@samsung.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/a8916ca1db6d994b38fd1569556e1b8654911ebf"},{"sha":"7bff73c6c9b2ed32de223aea6d8fc642bf573502","author":{"name":"Nikhilesh Reddy","email":"1e32cc90766364d327453cc38b968b137a000d78@codeaurora.org"},"message":"fs: Workaround the compiler's bad optimization\n\nWhen compiling the kernel with  the compiler\n\"aarch64-linux-android-gcc (GCC) 4.9.x-google 20140827 (prerelease)\"\nThe compiler seems to be optimizing a value out in the do_sync_write\nfunction and is incorrectly passing the pointer instead of the\ndereferenced value.\nForce the compiler to use the right value by passing the dereferenced\npointer instead of another variable that is assigned with the dereferenced\nvalue.\n\nChange-Id: I60505ffe39393f6323dcc7c6f912c74ea6aca6cd\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/7bff73c6c9b2ed32de223aea6d8fc642bf573502"},{"sha":"944c5806365ce6c7aadfb78f8aa74722f1b7c3e6","author":{"name":"franciscofranco","email":"0ac3193ff3d7b4e68ae404d59f776924e2be9ac9@gmail.com"},"message":"Added fsync on/off support.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/944c5806365ce6c7aadfb78f8aa74722f1b7c3e6"},{"sha":"e4a3aa83f1984de61981c12b61ad6843465ce6f0","author":{"name":"flar2","email":"54baee86d9719f38bf07b54ac189c5126488f211@gmail.com"},"message":"Add SIO and FIOPS i/o schedulers\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/e4a3aa83f1984de61981c12b61ad6843465ce6f0"},{"sha":"713657e76414ad8eb6476d8be46da20c13c40650","author":{"name":"flar2","email":"54baee86d9719f38bf07b54ac189c5126488f211@gmail.com"},"message":"FIOPS: update for linux 3.18","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/713657e76414ad8eb6476d8be46da20c13c40650"},{"sha":"ffd414163f252c23f10f22adb9131508f9dc0061","author":{"name":"flar2","email":"54baee86d9719f38bf07b54ac189c5126488f211@gmail.com"},"message":"SIO: update for linux 3.18","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/ffd414163f252c23f10f22adb9131508f9dc0061"},{"sha":"513d7029ef565363081837c5e2889930d4cc4fd7","author":{"name":"Paolo Valente","email":"0746d5f4a6f626638aa0b8efd4c4604c7ad14e9c@unimore.it"},"message":"block: cgroups, kconfig, build bits for BFQ-v7r8-3.18.0\n\nUpdate Kconfig.iosched and do the related Makefile changes to include\nkernel configuration options for BFQ. Also add the bfqio controller\nto the cgroups subsystem.\n\nSigned-off-by: Paolo Valente <paolo.valente@unimore.it>\nSigned-off-by: Arianna Avanzini <avanzini.arianna@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/513d7029ef565363081837c5e2889930d4cc4fd7"},{"sha":"5d42d1205578c2dcfa2960074f94859a1c87d784","author":{"name":"myfluxi","email":"95ab61bb01957fc548ef82d227666a28af3268a6@arcor.de"},"message":"PM: devfreq: Use high priority workqueue\n\nIt does not make sense to run kgsl on high and devfreq on regular\npriority.\n\nChange-Id: Ie5e6c9353a4e1324a6a49278e5ad3638462f551c\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/5d42d1205578c2dcfa2960074f94859a1c87d784"},{"sha":"d4f006e8f205eb7d14e644ad1068dfa24dfdaa2e","author":{"name":"Manikanta Sivapala","email":"428a3f87334f288c251029b816bd508b18e63130@codeaurora.org"},"message":"msm: vidc: disable CPU L2 cache PC during video sessions\n\nCPU L2 cache is being power collapsed and resumed during\nvideo sessions which is consuming more power unnecessarily.\nSo disable CPU L2 cache power collapse during video sessions\nusing qos requests to save power.\n\nChange-Id: Iaf47231bed1304510ea221b9d50866d3b4adfed0\nSigned-off-by: Maheshwar Ajja <majja@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/d4f006e8f205eb7d14e644ad1068dfa24dfdaa2e"},{"sha":"4de86c174d138f044596322b529dc15ce9608b40","author":{"name":"Steve Kondik","email":"5eb4f8ae09d1b5661f1add989b1c3fabe443bd83@cyngn.com"},"message":"qpnp-haptic: Dejank the haptics\n\n* Remove OEM patch which actually makes the jank worse\n * Add mutexes and call hap_set without the workqueue for direct mode\n\nChange-Id: I98f5b8ddea572def2706ad2cfa18f9dd460757ed","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/4de86c174d138f044596322b529dc15ce9608b40"},{"sha":"98f75880426c1bca3e8721cbdfabfcb8c21cc8bd","author":{"name":"andip71","email":"e6ecbe9226906ebc6c74fcf434eb9f5addb9e0e0@gmx.de"},"message":"block: add zen scheduler\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Wzedlare/kernel_cedric/commits/98f75880426c1bca3e8721cbdfabfcb8c21cc8bd"}]}
{"actor":{"display_login":"Wzedlare"}}