From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Frans Pop <elendil@planet.nl>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Stable Team <stable@kernel.org>
Subject: Re: [stable] [GIT pull] hrtimer fixes
Date: Mon, 18 Feb 2008 11:52:24 -0800 [thread overview]
Message-ID: <20080218195224.GA17538@kroah.com> (raw)
In-Reply-To: <20080218045856.745e42b8.akpm@linux-foundation.org>
On Mon, Feb 18, 2008 at 04:58:56AM -0800, Andrew Morton wrote:
> On Thu, 14 Feb 2008 13:45:42 -0800 Greg KH <greg@kroah.com> wrote:
>
> > On Thu, Feb 14, 2008 at 10:37:49PM +0100, Thomas Gleixner wrote:
> > > On Thu, 14 Feb 2008, Greg KH wrote:
> > >
> > > > On Thu, Feb 14, 2008 at 10:19:23PM +0100, Thomas Gleixner wrote:
> > > > > Linus,
> > > > >
> > > > > please pull hrtimer fixes from:
> > > > >
> > > > > ssh://master.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-hrt.git master
> > > > >
> > > > > The first patch fixes an overflow problem, which is caused by missing
> > > > > checks in the relative to absolute time conversion in the futex
> > > > > code. It got caught by the WARN_ON() in clockevents_program_event().
> > > > >
> > > > > The second patch prevents a false positive of the same WARN_ON().
> > > > >
> > > > > Fixes are confirmed to solve http://lkml.org/lkml/2008/2/10/137
> > > >
> > > > Are one of these needed in the stable tree?
> > >
> > > Yes, both are for stable as well. The report was against 2.6.24 stable
> >
> > Cool. But the stable team deals with individual patches, not git pulls.
> > Can you send us the individual patches when they hit Linus's tree?
> >
>
> Confused. That assertion appears to conflict with your earlier
>
> "you can just add a: Cc: stable <stable@kernel.org> to the signed-off-by
> area, and we (the stable tree developers) will get an automated email
> when it goes into Linus's tree, with the git changelog entry."
Hm, no, we still deal with patches, and unless Thomas had added that to
his patches, we would not have seen it. He was asking us to pull a git
tree :)
I guess I need to write up a "best way to deal with the stable tree"
type email and send it out to try to remove any confusion here. But
that will have to wait until tonight, it's a nice day out, a rarity this
time of year, and I'm supposed to not be working today, time to go take
the kids and play outside...
thanks,
greg k-h
prev parent reply other threads:[~2008-02-18 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 21:19 [GIT pull] hrtimer fixes Thomas Gleixner
2008-02-14 21:26 ` [stable] " Greg KH
2008-02-14 21:37 ` Thomas Gleixner
2008-02-14 21:45 ` Greg KH
2008-02-14 21:56 ` Thomas Gleixner
2008-02-18 12:58 ` Andrew Morton
2008-02-18 19:52 ` Greg KH [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=20080218195224.GA17538@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.