public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
	Josh Triplett <josh@joshtriplett.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] rcu: Deinline rcu_read_lock_sched_held() if DEBUG_LOCK_ALLOC
Date: Tue, 26 May 2015 08:51:54 -0700	[thread overview]
Message-ID: <20150526155153.GG5989@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150526113714.403b743a@gandalf.local.home>

On Tue, May 26, 2015 at 11:37:14AM -0400, Steven Rostedt wrote:
> On Tue, 26 May 2015 08:18:03 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> 
> > Steve, are you OK with Denys's most recent patch?
> 
> The only comment I believe I had on it was the use of parenthesis
> around the CONFIG names for defined(), as that seems to be the common
> method used in the kernel.

So it sounds the next step is for Denys to send an update with the
parentheses.

							Thanx, Paul


      parent reply	other threads:[~2015-05-26 15:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 10:04 [PATCH] rcu: Deinline rcu_read_lock_sched_held() if DEBUG_LOCK_ALLOC Denys Vlasenko
2015-05-21 12:52 ` Paul E. McKenney
2015-05-21 13:09   ` Steven Rostedt
2015-05-21 13:25     ` Paul E. McKenney
2015-05-21 13:41       ` Steven Rostedt
2015-05-21 13:45 ` Steven Rostedt
2015-05-21 15:09   ` Denys Vlasenko
2015-05-21 15:26     ` Paul E. McKenney
2015-05-21 21:53       ` Denys Vlasenko
2015-05-26 15:18         ` Paul E. McKenney
2015-05-26 15:37           ` Steven Rostedt
2015-05-26 15:47             ` Denys Vlasenko
2015-05-26 15:51             ` Paul E. McKenney [this message]

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=20150526155153.GG5989@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=dvlasenk@redhat.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=oleg@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tj@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