From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: unsigned commits in the rcu tree
Date: Wed, 17 May 2017 15:36:37 -0700 [thread overview]
Message-ID: <20170517223637.GN3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170518081417.2f724fbb@canb.auug.org.au>
On Thu, May 18, 2017 at 08:14:17AM +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> I noticed a couple of commits in the rcu tree today that have no
> Signed-off-by lines:
>
> 0eeaaea315cd fixup! rcu: Remove nohz_full full-system-idle state machine
> cbe476cef633 fixup! rcu: Remove debugfs tracing
>
> Please fix them up.
Will do!
Just for completeness, these are --fixup commits, which will be rebased
into the commits that they are fixing up.
Thanx, Paul
prev parent reply other threads:[~2017-05-17 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 22:14 linux-next: unsigned commits in the rcu tree Stephen Rothwell
2017-05-17 22:36 ` 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=20170517223637.GN3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).