)]}'
{
  "commit": "395913d0b1db37092ea3d9d69b832183b1dd84c5",
  "tree": "2b1aff8df27bfb02332ee4fe207a989244583c0a",
  "parents": [
    "0e625ac153126a0a62b7635fa9dc91f87ff39e38"
  ],
  "author": {
    "name": "Mathieu Desnoyers",
    "email": "mathieu.desnoyers@polymtl.ca",
    "time": "Mon Jun 08 13:17:31 2009 -0400"
  },
  "committer": {
    "name": "Dave Jones",
    "email": "davej@redhat.com",
    "time": "Tue Sep 01 12:45:18 2009 -0400"
  },
  "message": "[CPUFREQ] remove rwsem lock from CPUFREQ_GOV_STOP call (second call site)\n\nremove rwsem lock from CPUFREQ_GOV_STOP call (second call site)\n\ncommit\t42a06f2166f2f6f7bf04f32b4e823eacdceafdc9\n\nMissed a call site for CPUFREQ_GOV_STOP to remove the rwlock taken around the\nteardown. To make a long story short, the rwlock write-lock causes a circular\ndependency with cancel_delayed_work_sync(), because the timer handler takes the\nread lock.\n\nNote that all callers to __cpufreq_set_policy are taking the rwsem. All sysfs\ncallers (writers) hold the write rwsem at the earliest sysfs calling stage.\n\nHowever, the rwlock write-lock is not needed upon governor stop.\n\nSigned-off-by: Mathieu Desnoyers \u003cmathieu.desnoyers@polymtl.ca\u003e\nAcked-by: Venkatesh Pallipadi \u003cvenkatesh.pallipadi@intel.com\u003e\nCC: rjw@sisk.pl\nCC: mingo@elte.hu\nCC: Shaohua Li \u003cshaohua.li@intel.com\u003e\nCC: Pekka Enberg \u003cpenberg@cs.helsinki.fi\u003e\nCC: Dave Young \u003chidave.darkstar@gmail.com\u003e\nCC: \"Rafael J. Wysocki\" \u003crjw@sisk.pl\u003e\nCC: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nCC: trenn@suse.de\nCC: sven.wegener@stealer.net\nCC: cpufreq@vger.kernel.org\nSigned-off-by: Dave Jones \u003cdavej@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4da28444b23559e28028cfa2f517993f41071520",
      "old_mode": 33188,
      "old_path": "drivers/cpufreq/cpufreq.c",
      "new_id": "3938c7817095d0747a44045b51cff3c680e6e78a",
      "new_mode": 33188,
      "new_path": "drivers/cpufreq/cpufreq.c"
    }
  ]
}