)]}'
{
  "commit": "9c17bcda991000351cb2373f78be7e4b1c44caa3",
  "tree": "769385b50e512a3aafa8735be23c199bf83c56e7",
  "parents": [
    "7205656ab48da29a95d7f55e43a81db755d3cb3a"
  ],
  "author": {
    "name": "Thomas Gleixner",
    "email": "tglx@linutronix.de",
    "time": "Wed Sep 03 21:37:08 2008 +0000"
  },
  "committer": {
    "name": "Thomas Gleixner",
    "email": "tglx@linutronix.de",
    "time": "Fri Sep 05 11:11:52 2008 +0200"
  },
  "message": "clockevents: prevent multiple init/shutdown\n\nWhile chasing the C1E/HPET bugreports I went through the clock events\ncode inch by inch and found that the broadcast device can be initialized\nand shutdown multiple times. Multiple shutdowns are not critical, but\nuseless waste of time. Multiple initializations are simply broken. Another\nCPU might have the device in use already after the first initialization and\nthe second init could just render it unusable again.\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": "3044a88357faf3e575f0f47930fa8bdc3c98c036",
      "old_mode": 33188,
      "old_path": "kernel/time/tick-broadcast.c",
      "new_id": "5744f40b26970cc3e928b3b9b3cf28bf2038710a",
      "new_mode": 33188,
      "new_path": "kernel/time/tick-broadcast.c"
    }
  ]
}