From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the rcu tree
Date: Wed, 17 May 2023 08:41:15 +1000 [thread overview]
Message-ID: <20230517084116.17be78d7@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
Hi all,
Commits
1d29b558483d ("tools/nolibc: remove LINUX_REBOOT_ constants")
09efff85e556 ("tools/nolibc: add testcase for fork()/waitpid()")
d9d16cc80854 ("tools/nolibc: s390: provide custom implementation for sys_fork")
c792624d254d ("tools/nolibc: validate C89 compatibility")
d7644912ea9c ("tools/nolibc: use C89 comment syntax")
9cd4e2eb852c ("tools/nolibc: use __inline__ syntax")
367742887f79 ("tools/nolibc: use standard __asm__ statements")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-05-16 22:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 22:41 Stephen Rothwell [this message]
2023-05-16 22:54 ` linux-next: Signed-off-by missing for commit in the rcu tree Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2024-02-07 20:39 Stephen Rothwell
2024-02-08 16:07 ` Paul E. McKenney
2023-06-08 22:31 Stephen Rothwell
2023-06-09 19:00 ` Paul E. McKenney
2023-06-08 22:27 Stephen Rothwell
2023-06-08 22:28 ` Stephen Rothwell
2023-06-09 4:08 ` Zhangjin Wu
2023-06-09 9:24 ` Willy Tarreau
2023-03-08 2:16 Stephen Rothwell
2023-03-08 17:41 ` Paul E. McKenney
2022-09-22 10:12 Stephen Rothwell
2022-09-22 13:55 ` Paul E. McKenney
2022-01-03 21:38 Stephen Rothwell
2022-01-03 23:33 ` Paul E. McKenney
2021-05-23 3:02 Stephen Rothwell
2021-05-24 3:49 ` Paul E. McKenney
2021-03-08 6:03 Stephen Rothwell
2021-03-09 5:24 ` Paul E. McKenney
2021-01-10 2:24 Stephen Rothwell
2021-01-10 5:15 ` Paul E. McKenney
2020-11-22 10:08 Stephen Rothwell
2020-11-22 10:09 ` Stephen Rothwell
2020-11-22 17:51 ` Paul E. McKenney
2020-09-29 22:37 Stephen Rothwell
2020-09-30 4:43 ` Paul E. McKenney
2020-09-17 3:26 Stephen Rothwell
2020-09-17 18:00 ` Paul E. McKenney
2020-09-22 22:35 ` Stephen Rothwell
2020-09-28 7:57 ` Peter Zijlstra
2020-09-28 17:33 ` Paul E. McKenney
2020-11-18 23:40 ` Paul E. McKenney
2020-02-12 22:25 Stephen Rothwell
2020-02-13 21:38 ` Joel Fernandes
2020-02-27 15:10 ` Paul E. McKenney
2019-10-28 20:53 Stephen Rothwell
2019-10-29 0:37 ` Paul E. McKenney
2018-04-23 21:48 Stephen Rothwell
2018-04-23 22:16 ` Paul E. McKenney
2018-02-26 22:38 Stephen Rothwell
2018-02-26 23:22 ` Paul E. McKenney
2017-11-29 0:51 Stephen Rothwell
2017-11-29 1:14 ` Paul E. McKenney
2017-11-29 2:48 ` Lihao Liang
2017-11-29 3:14 ` Hanjun Guo
2017-11-29 3:29 ` Lihao Liang
2017-11-29 20:54 ` Paul E. McKenney
2017-07-30 13:48 Stephen Rothwell
2017-07-30 16:57 ` 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=20230517084116.17be78d7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@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;
as well as URLs for NNTP newsgroup(s).