From: "Paul E. McKenney" <paulmck@kernel.org>
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: Sat, 16 May 2020 10:05:05 -0700 [thread overview]
Message-ID: <20200516170505.GB2639@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200514230148.GB2869@paulmck-ThinkPad-P72>
On Thu, May 14, 2020 at 04:01:48PM -0700, Paul E. McKenney wrote:
> On Fri, May 15, 2020 at 08:43:17AM +1000, Stephen Rothwell wrote:
> > Hi all,
> > Commits
> >
> > b2998782ded4 ("Documentation/litmus-tests: Clarify about the RCU pre-initialization test")
> > 663f9202eb8a ("Documentation/litmus-tests: Merge atomic's README into top-level one")
> > f5eff20366f6 ("tools/memory-model: Fix reference to litmus test in recipes.txt")
> >
> > are missing a Signed-off-by from their committer.
>
> I knew I was forgetting something... Will fix, and thank you!!!
And fixed. But I didn't want you to be too bored, so I have also merged
with the noinstr-rcu-nmi-2020-05-15 branch of Thomas's and Peter's series. ;-)
https://lore.kernel.org/lkml/20200515234547.710474468@linutronix.de/
Thanx, Paul
next prev parent reply other threads:[~2020-05-16 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 22:43 linux-next: Signed-off-by missing for commits in the rcu tree Stephen Rothwell
2020-05-14 23:01 ` Paul E. McKenney
2020-05-16 17:05 ` Paul E. McKenney [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 4:18 Stephen Rothwell
2021-06-25 14:18 ` Paul E. McKenney
2021-01-12 22:03 Stephen Rothwell
2021-01-13 0:19 ` Paul E. McKenney
2020-06-20 22:06 Stephen Rothwell
2020-06-21 15:53 ` Paul E. McKenney
2018-06-26 23:04 Stephen Rothwell
2018-06-26 23:43 ` 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=20200516170505.GB2639@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--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