{"push_id":1395422390,"size":479,"distinct_size":479,"ref":"refs/heads/32.2.A.0.305_RyTek--CAF-based","head":"1bb149d49834d32dd04e32e11cf7c44505ef14d9","before":"690d0ac3a21f17c4efd9e0a36d9158bfcd0d199d","commits":[{"sha":"4e3611c0e83626335fc8777d9ddf7312617ad348","author":{"name":"Angelo G. Del Regno -- EternityProject Team Manager","email":"c633c68dd3fd792ca29f59c86ed3acbf7de59c65@gmail.com"},"message":"sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire\n\nThe original patch is by Klaus Ripke, but I can't find a commit to\ncherry-pick, so I'm linking the study on there: http://ripke.com/loadavg/moire\n\nAlso, here's the author's comment:\n\nWith some seconds based load (like SSL heartbeats)\nand LOAD_FREQ at (5*HZ+1) I see Moire patterns like inverse sawtooth,\nsince 2 or 3 probes hit the jobs (load increases quickly),\nfollowed by several probes missing it.\n\nA 4.61 sec interval gives optimal distribution over when within a\nsecond a probe is taken, as .61 is close to golden ratio phi 1.618...\n(test in http://ripke.com/goldenratio.c).\n\n12*4.61 = 55.32 secs is still close to a minute,\nand 13*4.61=59.93 is even closer than the current 12*5.01=60.12\n(with exponents EXP_x adjusted to a ratio of 13 instead of 12).","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/4e3611c0e83626335fc8777d9ddf7312617ad348"},{"sha":"2c57147df3dd3f134d08791b980f173d2d64ec62","author":{"name":"Pavankumar Kondeti","email":"1af0c446304ab4a0bcd7a34b51f44289b0b5ba30@codeaurora.org"},"message":"sched: don't inherit initial task load from the parent\n\nchild task is not supposed to inherit initial task load attribute\nfrom the parent. Reset the child's init_load_pct attribute during\nfork.\n\nChange-Id: I458b121f10f996fda364e97b51aaaf6c345c1dbb\nSigned-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/2c57147df3dd3f134d08791b980f173d2d64ec62"},{"sha":"0015b5061aab8175a60679dd92a84586b9e24766","author":{"name":"Pavankumar Kondeti","email":"1af0c446304ab4a0bcd7a34b51f44289b0b5ba30@codeaurora.org"},"message":"sched: don't inflate the task load when the CPU max freq is restricted\n\nWhen the CPU max freq is restricted and the CPU is running at the\nmax freq, the task load is inflated by max_possible_freq/max_freq\nfactor. This results in tasks migrating early to the better capacity\nCPUs which makes things worse if the frequency restriction is due\nto the thermal condition.\n\nChange-Id: Ie0ea405d7005764a6fb852914e88cf97102c138a\nSigned-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/0015b5061aab8175a60679dd92a84586b9e24766"},{"sha":"1d3e32604c9f6c695d56e22eb11223594312f3fb","author":{"name":"Syed Rameez Mustafa","email":"d0cb06bd5d626529e5ca7f6aba1e2023bbe2ea99@codeaurora.org"},"message":"sched: Add load based placement for RT tasks\n\nCurrently RT tasks prefer to go to the lowest power CPU in the\nsystem. This can end up causing contention on the lowest power\nCPU. Instead ensure that RT tasks end up on the lowest power\ncluster and the least loaded CPU within that cluster.\n\nChange-Id: I363b3d43236924962c67d2fb5d3d2d09800cd994\nSigned-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/1d3e32604c9f6c695d56e22eb11223594312f3fb"},{"sha":"bb6615546ba9afe38d2693140763ba025a1f5927","author":{"name":"Pavankumar Kondeti","email":"1af0c446304ab4a0bcd7a34b51f44289b0b5ba30@codeaurora.org"},"message":"sched: auto adjust the upmigrate and downmigrate thresholds\n\nThe load scale factor of a CPU gets boosted when its max freq\nis restricted. A task load at the same frequency is scaled higher\nthan normal under this scenario. This results in tasks migrating\nearly to the better capacity CPUs and their residency over there\nalso gets increased as their inflated load would be relatively\nhigher than than the downmigrate threshold.\n\nAuto adjust the upmigrate and downmigrate thresholds by a factor\nequal to  rq->max_possible_freq/rq->max_freq of a lower capacity CPU.\nIf the adjusted upmigrate threshold exceeds the window size, it is\nclipped to the window size. If the adjusted downmigrate threshold\ndecreases the difference between the upmigrate and downmigrate, it is\nclipped to a value such that the difference between the modified\nand the original thresholds is same.\n\nChange-Id: Ifa70ee5d4ca5fe02789093c7f070c77629907f04\nSigned-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/bb6615546ba9afe38d2693140763ba025a1f5927"},{"sha":"85bf17923b357ff6856ffd16ffa6485a83e21726","author":{"name":"Joonwoo Park","email":"c8d71ca0229c96429b0e81dc3c959fd598c45475@codeaurora.org"},"message":"sched: optimize power cost/freq estimation\n\nAt present, calculation of frequency estimation and power cost at the\nprojected frequency for a given task takes big portion of function\nselect_best_cpu() latency.  This is because function power_cost()\ncalculates and converts the task's demand to projected frequency to\nestimated power cost from select_best_cpu() path.\n\nIntroduce pre-calculated power cost and freqeuency per demand table to use\npre-calculated power cost rather than calculating these on the fly to\noptimize the function power_cost().  This change is solely for optimization\npurpose.\n\nCRs-fixed: 849655\nChange-Id: I0972a0b99dad1115cd41fb85785e5afae7138fd1\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/85bf17923b357ff6856ffd16ffa6485a83e21726"},{"sha":"e3f28889eb456145d04bb50ecfb07cc40ea62998","author":{"name":"Joonwoo Park","email":"c8d71ca0229c96429b0e81dc3c959fd598c45475@codeaurora.org"},"message":"sched: optimize select_best_cpu() with same power cost CPU mask\n\nAt present, the function select_best_cpu() has to continue to iterate the\nsearch CPUs for the possibility of finding a more power efficient CPU even\nif the best CPU based on cstate already found.  We can avoid this\nunnecessary search if it is known ahead of time that CPUs in a cluster\nhave the same power efficiency.\n\nIntroduce kernel parameter 'sched_same_power_cost_cpus' to inform the\nCPU mask that has an identical power costs and optimize the 'for' loop of\nselect_best_cpu() by ruling out CPUs that cannot be more power efficient\nthan cstate based best CPU with the same power cost CPU mask.\n\nCRs-fixed: 849655\nChange-Id: I9d2e7f560282a914fd0373aac6714353b9d1e36c\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\n\nConflicts:\n\tkernel/sched/fair.c\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/e3f28889eb456145d04bb50ecfb07cc40ea62998"},{"sha":"9fe63bdcbcd5f399875645148cd63d7a8de3149d","author":{"name":"Jiangli Yuan","email":"262c8d0b42107a39539c9f46514fab01ec871d37@motorola.com"},"message":"IKSWM-5880:sched/rt: really force updates rq clock in pick_next_task_rt\n\n In the original patch of \"sched: Fix inaccurate accounting for real-time\n task\", it will skip the update_rq_clock() if skip_clock_update is zero/-1.\n\n Fix this bug to make the original patch really force updates rq clock,\n then the realtime task's exec_start will be accurate.\n\nChange-Id: I235917648f1631f9f037fa12e8322488dcfa08a2\nSigned-off-by: Jiangli Yuan <jlyuan@motorola.com>\nReviewed-on: http://gerrit.mot.com/788261\nSME-Granted: SME Approvals Granted\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Zhi-Ming Yuan <a14194@motorola.com>\nReviewed-by: Yi-Wei Zhao <gbjc64@motorola.com>\nReviewed-by: Russell Knize <rknize@motorola.com>\nReviewed-by: Christopher Fries <cfries@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/RyTekk/sony_kernel_kitakami_8994/commits/9fe63bdcbcd5f399875645148cd63d7a8de3149d"},{"sha":"c0e8baee3b6be975ccae34fb852483823d1e8594","author":{"name":"franciscofranco","email":"0ac3193ff3d7b4e68ae404d59f776924e2be9ac9@gmail.com"},"message":"sched/fair: Stop searching for tasks in newidle balance if there are runnable tasks\n\nIt was found that when running some workloads (such as AIM7) on large\nsystems with many cores, CPUs do not remain idle for long. Thus, tasks\ncan wake/get enqueued while doing idle balancing.\n\nIn this patch, while traversing the domains in idle balance, in\naddition to checking for pulled_task, we add an extra check for\nthis_rq->nr_running for determining if we should stop searching for\ntasks to pull. If there are runnable tasks on this rq, then we will\nstop traversing the domains. This reduces the chance that idle balance\ndelays a task from running.\n\nThis patch resulted in approximately a 6% performance improvement when\nrunning a Java Server workload on an 8 socket machine.\n\nSigned-off-by: Jason Low <jason.low2@hp.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: daniel.lezcano@linaro.org\nCc: alex.shi@linaro.org\nCc: preeti@linux.vnet.ibm.com\nCc: efault@gmx.de\nCc: vincent.guittot@linaro.org\nCc: morten.rasmussen@arm.com\nCc: aswin@hp.com\nCc: chegu_vinod@hp.com\nLink: http://lkml.kernel.org/r/1398303035-18255-4-git-send-email-jason.low2@hp.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/c0e8baee3b6be975ccae34fb852483823d1e8594"},{"sha":"a0960d31985bf160eac7d852fc3db272d266f5dc","author":{"name":"franciscofranco","email":"0ac3193ff3d7b4e68ae404d59f776924e2be9ac9@gmail.com"},"message":"sched/balancing: Reduce the rate of needless idle load balancing\n\nThe current no_hz idle load balancer do load balancing for *all* idle cpus,\neven though the time due to load balance for a particular\nidle cpu could be still a while in the future.  This introduces a much\nhigher load balancing rate than what is necessary.  The patch\nchanges the behavior by only doing idle load balancing on\nbehalf of an idle cpu only when it is due for load balancing.\n\nOn SGI's systems with over 3000 cores, the cpu responsible for idle balancing\ngot overwhelmed with idle balancing, and introduces a lot of OS noise\nto workloads.  This patch fixes the issue.\n\nSigned-off-by: Tim Chen <tim.c.chen@linux.intel.com>\nAcked-by: Russ Anderson <rja@sgi.com>\nReviewed-by: Rik van Riel <riel@redhat.com>\nReviewed-by: Jason Low <jason.low2@hp.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Len Brown <len.brown@intel.com>\nCc: Dimitri Sivanich <sivanich@sgi.com>\nCc: Hedi Berriche <hedi@sgi.com>\nCc: Andi Kleen <andi@firstfloor.org>\nCc: MichelLespinasse <walken@google.com>\nCc: Peter Hurley <peter@hurleysoftware.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nLink: http://lkml.kernel.org/r/1400621967.2970.280.camel@schen9-DESK\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/a0960d31985bf160eac7d852fc3db272d266f5dc"},{"sha":"6de3682f73dd7e1deb1c1fb7725f2556feade228","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched: Optimize task_sched_runtime()\n\nLarge multi-threaded apps like to hit this using do_sys_times() and\nthen queue up on the rq->lock.\n\nAvoid when possible.\n\nLarry reported ~20% performance increase his test case.\n\nReported-by: Larry Woodman <lwoodman@redhat.com>\nSuggested-by: Paul Turner <pjt@google.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nCc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nLink: http://lkml.kernel.org/r/20131111172925.GG26898@twins.programming.kicks-ass.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/6de3682f73dd7e1deb1c1fb7725f2556feade228"},{"sha":"9e85782beca597b063702201618a247632725dba","author":{"name":"Joonwoo Park","email":"c8d71ca0229c96429b0e81dc3c959fd598c45475@codeaurora.org"},"message":"sched: avoid unnecessary HMP scheduler stat re-accounting\n\nWhen sched_entity's runnable average changes, before and after, we\ndecrease and increase HMP scheduler's statistics of the sched_entity to\ntake into account of updated runnable average.  In that period, however,\nother CPUs would see that the runnable average updating CPU's load as\nless than actual.  This is suboptimal and can lead improper task placement\nand load balance decision.\n\nWe can avoid such situation at least with window based load tracking as\nsched_entity's load average which is for PELT won't affect to HMP\nscheduler's load tracking statistics.  Thus fix to update HMP statistics\nonly when HMP scheduler uses PELT based load statistics.\n\nChange-Id: I9eb615c248c79daab5d22cbb4a994f94be6a968d\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/9e85782beca597b063702201618a247632725dba"},{"sha":"d680e8d063b61f6efbaf0c0e8acf09acecdb39aa","author":{"name":"Vegard Nossum","email":"9c44e0ed746b5c309b0bf31e4bae8fb5eb72beb1@oracle.com"},"message":"sched: Fix information leak in sys_sched_getattr()\n\nWe're copying the on-stack structure to userspace, but forgot to give\nthe right number of bytes to copy. This allows the calling process to\nobtain up to PAGE_SIZE bytes from the stack (and possibly adjacent\nkernel memory).\n\nThis fix copies only as much as we actually have on the stack\n(attr->size defaults to the size of the struct) and leaves the rest of\nthe userspace-provided buffer untouched.\n\nFound using kmemcheck + trinity.\n\nFixes: d50dde5a10f30 (\"sched: Add new scheduler syscalls to support an extended scheduling parameters ABI\")\n\nBug: 28731691\nChange-Id: Iaf2ecb4d2b0fa9df09539f2fc9ad6fd123d87aa2\nCc: Dario Faggioli <raistlin@linux.it>\nCc: Juri Lelli <juri.lelli@gmail.com>\nCc: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Vegard Nossum <vegard.nossum@oracle.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1392585857-10725-1-git-send-email-vegard.nossum@oracle.com\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/d680e8d063b61f6efbaf0c0e8acf09acecdb39aa"},{"sha":"0a624a81d7e986d08521c26aaa037d9c8a820e16","author":{"name":"Joonwoo Park","email":"c8d71ca0229c96429b0e81dc3c959fd598c45475@codeaurora.org"},"message":"sched: fix incorrect wait time and wait count statistics\n\nScheduler at present resets task's wait start timestamp when task migrates\nto another rq.  This misleads scheduler itself into reporting less wait\ntime than actual by omitting time spent for waiting prior to migration and\nalso more wait count than actual by counting migration as wait end event\nwhich can be seen by trace or /proc/<pid>/sched with CONFIG_SCHEDSTATS=y.\n\nCarry forward migrating task's wait time prior to migration and don't count\nmigration as a wait-end event to fix such statistics error.\n\nChange-Id: I0f6badf8072fc37826e4476ac2d1195e82b65bf1\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/0a624a81d7e986d08521c26aaa037d9c8a820e16"},{"sha":"ac8d363080ebc5ebdf31afa87959ade036711328","author":{"name":"Sasha Levin","email":"3eff170737f7f759a98f81ff6bf07d3c251c0277@oracle.com"},"message":"sched/core: Remove false-positive warning from wake_up_process()\n\ncommit 119d6f6a3be8b424b200dcee56e74484d5445f7e upstream.\n\nBecause wakeups can (fundamentally) be late, a task might not be in\nthe expected state. Therefore testing against a task's state is racy,\nand can yield false positives.\n\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: oleg@redhat.com\nFixes: 9067ac85d533 (\"wake_up_process() should be never used to wakeup a TASK_STOPPED/TRACED task\")\nLink: http://lkml.kernel.org/r/1448933660-23082-1-git-send-email-sasha.levin@oracle.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\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/RyTekk/sony_kernel_kitakami_8994/commits/ac8d363080ebc5ebdf31afa87959ade036711328"},{"sha":"0db1c29128fe5105b216c8597e4621526a3b5389","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"sched/cputime: Fix steal time accounting vs. CPU hotplug\n\ncommit e9532e69b8d1d1284e8ecf8d2586de34aec61244 upstream.\n\nOn CPU hotplug the steal time accounting can keep a stale rq->prev_steal_time\nvalue over CPU down and up. So after the CPU comes up again the delta\ncalculation in steal_account_process_tick() wreckages itself due to the\nunsigned math:\n\n\t u64 steal = paravirt_steal_clock(smp_processor_id());\n\n\t steal -= this_rq()->prev_steal_time;\n\nSo if steal is smaller than rq->prev_steal_time we end up with an insane large\nvalue which then gets added to rq->prev_steal_time, resulting in a permanent\nwreckage of the accounting. As a consequence the per CPU stats in /proc/stat\nbecome stale.\n\nNice trick to tell the world how idle the system is (100%) while the CPU is\n100% busy running tasks. Though we prefer realistic numbers.\n\nNone of the accounting values which use a previous value to account for\nfractions is reset at CPU hotplug time. update_rq_clock_task() has a sanity\ncheck for prev_irq_time and prev_steal_time_rq, but that sanity check solely\ndeals with clock warps and limits the /proc/stat visible wreckage. The\nprev_time values are still wrong.\n\nSolution is simple: Reset rq->prev_*_time when the CPU is plugged in again.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nAcked-by: Rik van Riel <riel@redhat.com>\nCc: <stable@vger.kernel.org>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Glauber Costa <glommer@parallels.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nFixes: commit 095c0aa83e52 \"sched: adjust scheduler cpu power for stolen time\"\nFixes: commit aa483808516c \"sched: Remove irq time from available CPU power\"\nFixes: commit e6e6685accfa \"KVM guest: Steal time accounting\"\nLink: http://lkml.kernel.org/r/alpine.DEB.2.11.1603041539490.3686@nanos\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Willy Tarreau <w@1wt.eu>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/0db1c29128fe5105b216c8597e4621526a3b5389"},{"sha":"dfff8ff0e3b2cc2fb9e3e9b0c856659b978833f7","author":{"name":"Joonwoo Park","email":"c8d71ca0229c96429b0e81dc3c959fd598c45475@codeaurora.org"},"message":"sched: encourage idle load balance and discourage active load balance\nEncourage IDLE and NEWLY_IDLE load balance by ignoring cache hotness and\ndiscourage active load balance when by increasing busy balancing failure\nthreshold to initiate active load balancer in order to reduce scheduler\nlatency and avoid unnecessary active migration within a same domain.\n\nChange-Id: I22f6aba11932ccbb82a436c0532589c46f9148ed\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\n[pkondeti@codeaurora.org: resolved minor merge conflicts]\nSigned-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>\n\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/dfff8ff0e3b2cc2fb9e3e9b0c856659b978833f7"},{"sha":"7fb607f45af1e8e4caa6e3a0107cbd9722d32473","author":{"name":"imoseyon","email":"10a51fa76245a6d62993b9f678997023cca4f98d@gmail.com"},"message":"cpufreq: show cpu voltages via sysfs\n\n* use the known sysfs node for compatibility","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/7fb607f45af1e8e4caa6e3a0107cbd9722d32473"},{"sha":"1a4fd563ef639f9027d09517977585f0a1c4381d","author":{"name":"Viresh Kumar","email":"4ca49bc1dcfdfc376d29da1eb07a3e0b3cd46daa@linaro.org"},"message":"cpufreq: remove unused notifier: CPUFREQ_{SUSPENDCHANGE|RESUMECHANGE}\n\nTwo cpufreq notifiers CPUFREQ_RESUMECHANGE and CPUFREQ_SUSPENDCHANGE have\nnot been used for some time, so remove them to clean up code a bit.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nReviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\n[rjw: Changelog]\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/1a4fd563ef639f9027d09517977585f0a1c4381d"},{"sha":"2ba5d578ec5f90a931d8d17e3555b80766cfc3dd","author":{"name":"Viresh Kumar","email":"4ca49bc1dcfdfc376d29da1eb07a3e0b3cd46daa@linaro.org"},"message":"cpufreq: use memcpy() to copy policy\n\ncpufreq_get_policy() is useful if the pointer to policy isn't available\nin advance. But if it is available, then there is no need to call\ncpufreq_get_policy(). Directly use memcpy() to copy the policy.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/2ba5d578ec5f90a931d8d17e3555b80766cfc3dd"}]}
{"actor":{"display_login":"RyTekk"}}