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: Signed-off-by missing for commits in the rcu tree
Date: Tue, 26 Jun 2018 16:43:52 -0700 [thread overview]
Message-ID: <20180626234352.GR3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180627090409.60641869@canb.auug.org.au>
On Wed, Jun 27, 2018 at 09:04:09AM +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> Commit
>
> aa838e0b70e1 ("MAINTAINERS: Add Daniel Lustig as an LKMM reviewer")
>
> is missing a Signed-off-by from its committer.
Will fix, apologies! I must have lost the '-s' argument to "git am".
> Please sort out the "Not-Yet-Signed-off-by: tags on commit
>
> 0cd34e83b2a5 ("rcu: Make expedited GPs handle CPU 0 being offline")
>
> Please remember that the linux-next tree is not a development tree,
> it is an integration testing tree.
This should be fixed in the most recent push of rcu/next, admittedly less
than two hours ago.
Thanx, Paul
next prev parent reply other threads:[~2018-06-26 23:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 23:04 linux-next: Signed-off-by missing for commits in the rcu tree Stephen Rothwell
2018-06-26 23:43 ` Paul E. McKenney [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-14 22:43 Stephen Rothwell
2020-05-14 23:01 ` Paul E. McKenney
2020-05-16 17:05 ` Paul E. McKenney
2020-06-20 22:06 Stephen Rothwell
2020-06-21 15:53 ` Paul E. McKenney
2021-01-12 22:03 Stephen Rothwell
2021-01-13 0:19 ` Paul E. McKenney
2021-06-25 4:18 Stephen Rothwell
2021-06-25 14:18 ` 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=20180626234352.GR3593@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).