mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <greg@kroah.com>
Cc: 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: Thu, 14 Feb 2008 22:37:49 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802142236440.12988@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080214212643.GA18521@kroah.com>

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
 
> If so, 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.

Will do next time.

Thanks,

	tglx

  reply	other threads:[~2008-02-14 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 21:19 Thomas Gleixner
2008-02-14 21:26 ` [stable] " Greg KH
2008-02-14 21:37   ` Thomas Gleixner [this message]
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

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.1.00.0802142236440.12988@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=elendil@planet.nl \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stable@kernel.org \
    --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®