From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: Oddball Author from on commit for rcu tree
Date: Sun, 8 Dec 2013 09:03:18 -0800 [thread overview]
Message-ID: <20131208170318.GA5013@kroah.com> (raw)
In-Reply-To: <CAB=NE6V3PMXC19k9nwv0fXfjCt7u+bY44-zBStSi_SFiDbVW8Q@mail.gmail.com>
On Sun, Dec 08, 2013 at 05:34:13PM +0100, Luis R. Rodriguez wrote:
> On Sun, Dec 8, 2013 at 5:32 PM, Luis R. Rodriguez
> <mcgrof@do-not-panic.com> wrote:
> > I see this commit on linux-next:
> >
> > commit 705e5a58432b56f9821d6884341575c02536661f
> > Author: Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> > Date: Thu Oct 10 11:08:33 2013 -0700
> >
> > rcu: Fix coccinelle warnings
> >
> > This commit fixes the following coccinelle warning:
> >
> > kernel/rcu/tree.c:712:9-10: WARNING: return of 0/1 in function
> > 'rcu_lockdep_current_cpu_online' with return type bool
> >
> > Return statements in functions returning bool should use
> > true/false instead of 1/0.
> > Generated by: coccinelle/misc/boolreturn.cocci
> >
> > Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >
> > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > index 3049950..f8c0299 100644
> > --- a/kernel/rcu/tree.c
> > +++ b/kernel/rcu/tree.c
> > @@ -725,7 +725,7 @@ bool rcu_lockdep_current_cpu_online(void)
> > bool ret;
> >
> > if (in_nmi())
> > - return 1;
> > + return true;
> > preempt_disable();
> > rdp = this_cpu_ptr(&rcu_sched_data);
> > rnp = rdp->mynode;
> >
> >
> > Although I'm enjoying the usage of the Generated by tag thing, the
> > From of that patch had the Signed-off-by tag, not sure how that
> > happened but if its going to happen more better we catch it now. Also
> > not sure if that will trigger a flag to Greg and Corbet's stat scripts
> > but just in case Cc'd.
>
> Doh, too late:
>
> mcgrof@cerro ~/linux-next (git::master)$ git log --pretty="%an" | grep Signed
> Signed-off-by: Fengguang Wu
> Signed-off-by: Sony Chacko
> Signed-off-by: Sony Chacko
> Signed-off-by: Jan Kara
> Signed-off-by: Darren Hart
> Signed-off-by: Darren Hart
> Signed-off-by: Darren Hart
> Signed-off-by: Wu Fengguang
> Signed-off-by: Peter Stokes
> Signed-off by Yi Yang
> Signed-off-by@vergenet.net":Simon
Odd, my tools don't seem to catch that, because it triggers off of the
email address more than the "name". Anyway, I'll fix it up in my
copy of "cleaned up kernel logs" that I keep to make things easier for
people who want to do things with the kernel logs.
thanks,
greg k-h
prev parent reply other threads:[~2013-12-08 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB=NE6VEGSm=3DVtbcopQYsF=nEneXyPioWaTTMJU-RdhoLOJg@mail.gmail.com>
2013-12-08 16:34 ` Oddball Author from on commit for rcu tree Luis R. Rodriguez
2013-12-08 17:03 ` Greg Kroah-Hartman [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=20131208170318.GA5013@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fengguang.wu@intel.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=paulmck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox