From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, John Stultz <johnstul@us.ibm.com>,
Prarit Bhargava <prarit@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT pull] leap second fixes for 3.5
Date: Sat, 14 Jul 2012 00:21:43 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1207140017080.32033@ionos> (raw)
In-Reply-To: <alpine.LFD.2.02.1207132132120.32033@ionos>
On Fri, 13 Jul 2012, Thomas Gleixner wrote:
> Linus,
>
> please pull the latest timers-urgent-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus
>
> 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
>
> 5baefd6: hrtimer: Update hrtimer base offsets each hrtimer_interrupt
> f6c06ab: timekeeping: Provide hrtimer update function
>
> are merily preventing the stuff loops forever issues, which people
> have observed.
I'm a moron. Copied from teh wrong direction. That should be:
f55a6fa: hrtimer: Provide clock_was_set_delayed()
4873fa0: timekeeping: Fix leapsecond triggered load spike issue
That are the two commits which do the basic damage containment.
Gah, I explicitely asked some involved person to look over that mail
before I sent it. :(
Grumbling out of a brown paperbag
tglx
prev parent reply other threads:[~2012-07-13 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 21:09 Thomas Gleixner
2012-07-13 22:21 ` Thomas Gleixner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1207140017080.32033@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®