{"push_id":1091924919,"size":1,"distinct_size":1,"ref":"refs/heads/android-m","head":"38e5ec0aa6f778b75c6b886f687e2b0190e02072","before":"1f094ef77a75067eb57d85f67a1efc16f9941044","commits":[{"sha":"38e5ec0aa6f778b75c6b886f687e2b0190e02072","author":{"email":"9ce5770b3bb4b2a1d59be2d97e34379cd192299f@cyngn.com","name":"Steve Kondik"},"message":"rootdir: Remove cpufreq mode settings\n\n * AFAIK we no longer should have anything which depends on system\n   server or settings writing to the cpufreq controls. Since new\n   devices have their cpufreq config nodes nested per-cpu, this\n   configuration is no longer valid. It also depends on sketchy\n   kernel patches which only work when the moon is in the correct\n   phase. Additionally, I see a lot of random logspam when\n   devices are hotplugged.\n * If a device needs this functionality, a better way to do it\n   is via a userspace daemon which is dedicated to the task since\n   it can poll() on the various states and get notified in realtime.\n\nChange-Id: Ib526663d760d6cb758e13f1fa29e7d6229de3daa","distinct":true,"url":"https://api.github.com/repos/AndroidRul3z/android_system_core/commits/38e5ec0aa6f778b75c6b886f687e2b0190e02072"}]}