)]}'
{
  "commit": "d55e5bd0201a2af0182687882a92c5f95dbccc12",
  "tree": "858da1717cd4491afeffd55791ea6b607062a7cd",
  "parents": [
    "5651721edec25bf73cee060150e684044eac42dc",
    "5baefd6d84163443215f4a99f6a20f054ef11236"
  ],
  "author": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Fri Jul 13 15:31:21 2012 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Fri Jul 13 15:31:21 2012 -0700"
  },
  "message": "Merge branch \u0027timers-urgent-for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull the leap second fixes from Thomas Gleixner:\n \"It\u0027s a rather large series, but well discussed, refined and reviewed.\n  It got a massive testing by John, Prarit and tip.\n\n  In theory we could split it into two parts.  The first two patches\n\n    f55a6faa3843: hrtimer: Provide clock_was_set_delayed()\n    4873fa070ae8: timekeeping: Fix leapsecond triggered load spike issue\n\n  are merely preventing the stuff loops forever issues, which people\n  have observed.\n\n  But there is no point in delaying the other 4 commits which achieve\n  full correctness into 3.6 as they are tagged for stable anyway.  And I\n  rather prefer to have the full fixes merged in bulk than a \"prevent\n  the observable wreckage and deal with the hidden fallout later\"\n  approach.\"\n\n* \u0027timers-urgent-for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n  hrtimer: Update hrtimer base offsets each hrtimer_interrupt\n  timekeeping: Provide hrtimer update function\n  hrtimers: Move lock held region in hrtimer_interrupt()\n  timekeeping: Maintain ktime_t based offsets for hrtimers\n  timekeeping: Fix leapsecond triggered load spike issue\n  hrtimer: Provide clock_was_set_delayed()\n",
  "tree_diff": []
}