From: Peter Zijlstra <peterz@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Gregory Haskins <ghaskins@novell.com>, stable <stable@kernel.org>,
mingo@elte.hu, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [stable] [PATCH] lockdep: fix mismatched lockdep_depth/curr_chain_hash
Date: Thu, 25 Oct 2007 19:48:02 +0200 [thread overview]
Message-ID: <1193334482.6914.23.camel@twins> (raw)
In-Reply-To: <20071008173908.GA26121@kroah.com>
On Mon, 2007-10-08 at 10:39 -0700, Greg KH wrote:
> On Mon, Oct 08, 2007 at 07:36:10PM +0200, Peter Zijlstra wrote:
> >
> > On Mon, 2007-10-08 at 10:24 -0700, Greg KH wrote:
> > > On Fri, Oct 05, 2007 at 11:31:26AM +0200, Peter Zijlstra wrote:
> > > >
> > > > Stable team,
> > > >
> > > > please consider this patch for the next 22-stable.
> > >
> > > I don't see this patch in Linus's upstream tree. We need it there to be
> > > able to accept it for -stable. Or is this just a bugfix of other things
> > > that are already in his tree?
> >
> > I send Linus a similar patch, haven??t seem him pick it up yet.
> > I??ll notify you when and if he picks it up.
>
> Great, that would be great for us -stable monkeys...
3aa416b07f0adf01c090baab26fb70c35ec17623
next prev parent reply other threads:[~2007-10-25 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 4:03 [PATCH] LOCKDEP: fix mismatched lockdep_depth/curr_chain_hash Gregory Haskins
2007-10-05 9:31 ` [PATCH] lockdep: " Peter Zijlstra
2007-10-08 17:24 ` [stable] " Greg KH
2007-10-08 17:36 ` Peter Zijlstra
2007-10-08 17:39 ` Greg KH
2007-10-25 17:48 ` Peter Zijlstra [this message]
2007-10-25 18:55 ` Chuck Ebbert
2007-10-31 14:37 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2007-10-31 15:03 Gregory Haskins
2007-10-31 15:44 Gregory Haskins
2007-10-31 16:24 ` [stable] " 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=1193334482.6914.23.camel@twins \
--to=peterz@infradead.org \
--cc=ghaskins@novell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.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