All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Michael Wang <wangyun@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 2/3] kmemleak: replace list_for_each_continue_rcu with new interface
Date: Fri, 24 Aug 2012 12:53:57 -0700	[thread overview]
Message-ID: <20120824195357.GR2472@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120824100505.GG7585@arm.com>

On Fri, Aug 24, 2012 at 11:05:05AM +0100, Catalin Marinas wrote:
> On Fri, Aug 24, 2012 at 01:52:50AM +0100, Michael Wang wrote:
> > On 08/17/2012 12:33 PM, Michael Wang wrote:
> > > From: Michael Wang <wangyun@linux.vnet.ibm.com>
> > > 
> > > This patch replaces list_for_each_continue_rcu() with
> > > list_for_each_entry_continue_rcu() to save a few lines
> > > of code and allow removing list_for_each_continue_rcu().
> > 
> > Could I get some comments on this patch?
> 
> Sorry, busy with other things and forgot about this.
> 
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Queued, thank you both!

							Thanx, Paul

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Michael Wang <wangyun@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 2/3] kmemleak: replace list_for_each_continue_rcu with new interface
Date: Fri, 24 Aug 2012 12:53:57 -0700	[thread overview]
Message-ID: <20120824195357.GR2472@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120824100505.GG7585@arm.com>

On Fri, Aug 24, 2012 at 11:05:05AM +0100, Catalin Marinas wrote:
> On Fri, Aug 24, 2012 at 01:52:50AM +0100, Michael Wang wrote:
> > On 08/17/2012 12:33 PM, Michael Wang wrote:
> > > From: Michael Wang <wangyun@linux.vnet.ibm.com>
> > > 
> > > This patch replaces list_for_each_continue_rcu() with
> > > list_for_each_entry_continue_rcu() to save a few lines
> > > of code and allow removing list_for_each_continue_rcu().
> > 
> > Could I get some comments on this patch?
> 
> Sorry, busy with other things and forgot about this.
> 
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Queued, thank you both!

							Thanx, Paul


  reply	other threads:[~2012-08-24 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <502CB92F.2010700@linux.vnet.ibm.com>
2012-08-17  4:33 ` [PATCH 2/3] kmemleak: replace list_for_each_continue_rcu with new interface Michael Wang
2012-08-17  4:33   ` Michael Wang
2012-08-21  0:02   ` Paul E. McKenney
2012-08-21  0:02     ` Paul E. McKenney
2012-08-24  0:52   ` Michael Wang
2012-08-24  0:52     ` Michael Wang
2012-08-24 10:05     ` Catalin Marinas
2012-08-24 10:05       ` Catalin Marinas
2012-08-24 19:53       ` Paul E. McKenney [this message]
2012-08-24 19:53         ` Paul E. McKenney

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=20120824195357.GR2472@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wangyun@linux.vnet.ibm.com \
    /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.