)]}'
{
  "commit": "757455d41c390da4ae8e06468ad097fe42eaab41",
  "tree": "da0d9bbc29d38c4dae625d2503acaed3ae776302",
  "parents": [
    "2737c49f29a29f3d3645ba0778aa7a8798f32249"
  ],
  "author": {
    "name": "Thomas Gleixner",
    "email": "tglx@linutronix.de",
    "time": "Thu Sep 17 17:31:09 2009 +0200"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@elte.hu",
    "time": "Tue Sep 13 11:12:02 2011 +0200"
  },
  "message": "locking, latencytop: Annotate latency_lock as raw\n\nThe latency_lock is lock can be taken in the guts of the\nscheduler code and therefore cannot be preempted on -rt -\nannotate it.\n\nIn mainline this change documents the low level nature of\nthe lock - otherwise there\u0027s no functional difference. Lockdep\nand Sparse checking will work as usual.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "376066e10413f5179c4f72ce3cbfc5c83744f5fc",
      "old_mode": 33188,
      "old_path": "kernel/latencytop.c",
      "new_id": "4ac8ebfcab599b79bc5becb2430f2412d85ca16c",
      "new_mode": 33188,
      "new_path": "kernel/latencytop.c"
    }
  ]
}