diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2012-07-13 15:31:21 -0700 | 
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-07-13 15:31:21 -0700 | 
| commit | d55e5bd0201a2af0182687882a92c5f95dbccc12 (patch) | |
| tree | 858da1717cd4491afeffd55791ea6b607062a7cd /lib/mpi/mpi-inv.c | |
| parent | 5651721edec25bf73cee060150e684044eac42dc (diff) | |
| parent | 5baefd6d84163443215f4a99f6a20f054ef11236 (diff) | |
Merge branch 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull the leap second fixes from Thomas Gleixner:
 "It's a rather large series, but well discussed, refined and reviewed.
  It got a massive testing by John, Prarit and tip.
  In theory we could split it into two parts.  The first two patches
    f55a6faa3843: hrtimer: Provide clock_was_set_delayed()
    4873fa070ae8: timekeeping: Fix leapsecond triggered load spike issue
  are merely preventing the stuff loops forever issues, which people
  have observed.
  But there is no point in delaying the other 4 commits which achieve
  full correctness into 3.6 as they are tagged for stable anyway.  And I
  rather prefer to have the full fixes merged in bulk than a "prevent
  the observable wreckage and deal with the hidden fallout later"
  approach."
* 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  hrtimer: Update hrtimer base offsets each hrtimer_interrupt
  timekeeping: Provide hrtimer update function
  hrtimers: Move lock held region in hrtimer_interrupt()
  timekeeping: Maintain ktime_t based offsets for hrtimers
  timekeeping: Fix leapsecond triggered load spike issue
  hrtimer: Provide clock_was_set_delayed()
Diffstat (limited to 'lib/mpi/mpi-inv.c')
0 files changed, 0 insertions, 0 deletions
