public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tejun Heo <tj@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Peter Zijlstra <peterz@infradead.org>, stable <stable@kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Eric Dumazet <dada1@cosmosbay.com>, Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [stable] [PATCH] lockdep fix incorrect percpu usage
Date: Mon, 19 Apr 2010 11:29:36 -0700	[thread overview]
Message-ID: <20100419182936.GI32347@kroah.com> (raw)
In-Reply-To: <4BB2B6C4.8090803@kernel.org>

On Wed, Mar 31, 2010 at 11:43:16AM +0900, Tejun Heo wrote:
> On 03/31/2010 12:05 AM, Mathieu Desnoyers wrote:
> > I see. These patches are "on their way" to mainline, so it's better not to
> > create conflicts. So the lockdep patch should only be applied to -stable, but
> > separate module.c patch should apply to both -stable and mainline. Am I
> > correct ?
> 
> I'll push proper fixes to mainline in a few days.  For -stable, yeah,
> probably.

Ok, did a patch ever end up in Linus's tree for this that I can pull
into the -stable releases?

thanks,

greg k-h

  reply	other threads:[~2010-04-19 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30  3:34 [PATCH] lockdep fix incorrect percpu usage Mathieu Desnoyers
2010-03-30  8:47 ` Peter Zijlstra
2010-03-30 13:45   ` Mathieu Desnoyers
2010-03-30 14:25     ` Peter Zijlstra
2010-03-30 15:05       ` Mathieu Desnoyers
2010-03-31  2:43         ` Tejun Heo
2010-04-19 18:29           ` Greg KH [this message]
2010-04-20 14:33             ` [stable] " Mathieu Desnoyers
2010-04-21 10:52               ` Tejun Heo

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=20100419182936.GI32347@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=dada1@cosmosbay.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=stable@kernel.org \
    --cc=tj@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