)]}'
{
  "log": [
    {
      "commit": "1dab2597e7d0591c2ee1bde29e8d51e5ba707acb",
      "tree": "c7b25327f1d6064581465e3aa044ed746518aedb",
      "parents": [
        "5eed1dbca45b0113b4a33a99c18fce86995ba55a"
      ],
      "author": {
        "name": "Mike Chan",
        "email": "mike@android.com",
        "time": "Tue Jun 22 11:26:45 2010 -0700"
      },
      "committer": {
        "name": "Colin Cross",
        "email": "ccross@android.com",
        "time": "Tue Jun 14 09:09:39 2011 -0700"
      },
      "message": "cpufreq: interactive: New \u0027interactive\u0027 governor\n\nThis governor is designed for latency-sensitive workloads, such as\ninteractive user interfaces.  The interactive governor aims to be\nsignificantly more responsive to ramp CPU quickly up when CPU-intensive\nactivity begins.\n\nExisting governors sample CPU load at a particular rate, typically\nevery X ms.  This can lead to under-powering UI threads for the period of\ntime during which the user begins interacting with a previously-idle system\nuntil the next sample period happens.\n\nThe \u0027interactive\u0027 governor uses a different approach. Instead of sampling\nthe CPU at a specified rate, the governor will check whether to scale the\nCPU frequency up soon after coming out of idle.  When the CPU comes out of\nidle, a timer is configured to fire within 1-2 ticks.  If the CPU is very\nbusy from exiting idle to when the timer fires then we assume the CPU is\nunderpowered and ramp to MAX speed.\n\nIf the CPU was not sufficiently busy to immediately ramp to MAX speed, then\nthe governor evaluates the CPU load since the last speed adjustment,\nchoosing the highest value between that longer-term load or the short-term\nload since idle exit to determine the CPU speed to ramp to.\n\nA realtime thread is used for scaling up, giving the remaining tasks the\nCPU performance benefit, unlike existing governors which are more likely to\nschedule rampup work to occur after your performance starved tasks have\ncompleted.\n\nThe tuneables for this governor are:\n/sys/devices/system/cpu/cpufreq/interactive/min_sample_time:\n\tThe minimum amount of time to spend at the current frequency before\n\tramping down. This is to ensure that the governor has seen enough\n\thistoric CPU load data to determine the appropriate workload.\n\tDefault is 80000 uS.\n/sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load\n\tThe CPU load at which to ramp to max speed.  Default is 85.\n\nChange-Id: Ib2b362607c62f7c56d35f44a9ef3280f98c17585\nSigned-off-by: Mike Chan \u003cmike@android.com\u003e\nSigned-off-by: Todd Poynor \u003ctoddpoynor@google.com\u003e\nBug: 3152864\n"
    },
    {
      "commit": "f0e733f32e56ded9309a8b8da3a77d47beb3cbdd",
      "tree": "88bd05d0c1f149a1889df525f8ce4777477cb6b0",
      "parents": [
        "72b2fd5cb89933a5b0dba32735d9b22ae3fb866e"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Sun May 15 19:34:29 2011 +0200"
      },
      "committer": {
        "name": "Linus Walleij",
        "email": "linus.walleij@linaro.org",
        "time": "Tue May 24 22:20:14 2011 +0200"
      },
      "message": "cpufreq: make DB8500 cpufreq driver compile\n\nConcluding interface update and movement of the driver by making\nthe DB8500 cpufreq driver compile in the cpufreq subsystem.\n\nCc: Arnd Bergmann \u003carnd@arndb.de\u003e\nAcked-by: Dave Jones \u003cdavej@redhat.com\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n"
    },
    {
      "commit": "bb0a56ecc4ba2a3db1b6ea6949c309886e3447d3",
      "tree": "680b1307d7d9c1a188b7483875f7a3287d8b51a0",
      "parents": [
        "1a8e1463a49aaa452da1cefe184a00d4df47f1ef"
      ],
      "author": {
        "name": "Dave Jones",
        "email": "davej@redhat.com",
        "time": "Thu May 19 18:51:07 2011 -0400"
      },
      "committer": {
        "name": "Dave Jones",
        "email": "davej@redhat.com",
        "time": "Thu May 19 18:51:07 2011 -0400"
      },
      "message": "[CPUFREQ] Move x86 drivers to drivers/cpufreq/\n\nSigned-off-by: Dave Jones \u003cdavej@redhat.com\u003e\n"
    },
    {
      "commit": "b9170836d1aa4ded7cc1ac1cb8fbc7867061c98c",
      "tree": "87fbac643c392c8ba2459158f78671c356e8dd4a",
      "parents": [
        "b53cc6ead046093477ec7a3354d620337101ea5b"
      ],
      "author": {
        "name": "Dave Jones",
        "email": "davej@redhat.com",
        "time": "Tue May 31 19:03:47 2005 -0700"
      },
      "committer": {
        "name": "Dave Jones",
        "email": "davej@redhat.com",
        "time": "Tue May 31 19:03:47 2005 -0700"
      },
      "message": "[CPUFREQ] Conservative cpufreq governer\n\nA new cpufreq module, based on the ondemand one with my additional patches\njust posted.  This one is more suitable for battery environments where its\nprobably more appealing to have the cpu freq gracefully increase and decrease\nrather than flip between the min and max freq\u0027s.\n\nN.B. Bruno Ducrot pointed out that the amd64\u0027s \"do have unacceptable latency\nbetween min and max freq transition, due to the step-by-step requirements\n(200MHz IIRC)\"; so AMD64 users would probably benefit from this too.\n\nSigned-off-by: Alexander Clouter \u003calex-kernel@digriz.org.uk\u003e\nSigned-off-by: Dave Jones \u003cdavej@redhat.com\u003e\n\n"
    },
    {
      "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
      "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d",
      "parents": [],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n"
    }
  ]
}