public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <srostedt@redhat.org>
Subject: Re: [PATCH 1/2] rcu: just rename call_rcu_bh instead of making it a macro
Date: Fri, 15 Aug 2008 17:54:52 +0200	[thread overview]
Message-ID: <20080815155452.GG27955@elte.hu> (raw)
In-Reply-To: <20080801211123.GE14851@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> On Wed, Jul 30, 2008 at 02:20:54PM -0400, Steven Rostedt wrote:
> > Seems that I found a box that has a config that passes call_rcu_bh as a
> > function pointer (see net/sctp/sm_make_chunk.c), so declaring the
> > call_rcu_bh has a macro function isn't good enough.
> > 
> > This patch makes it just another name of call_rcu for rcupreempt.
> 
> Looks good!
> 
> Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

applied to tip/core/rcu - thanks!

	Ingo

  reply	other threads:[~2008-08-15 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 18:20 [PATCH 0/2] RCU preempt updates Steven Rostedt
2008-07-30 18:20 ` [PATCH 1/2] rcu: just rename call_rcu_bh instead of making it a macro Steven Rostedt
2008-08-01 21:11   ` Paul E. McKenney
2008-08-15 15:54     ` Ingo Molnar [this message]
2008-07-30 18:20 ` [PATCH 2/2] rcu: trace fix possible mem-leak Steven Rostedt
2008-08-01 21:11   ` Paul E. McKenney
2008-08-15 15:55     ` Ingo Molnar

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=20080815155452.GG27955@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=srostedt@redhat.org \
    --cc=tglx@linutronix.de \
    /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