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 commits in the rcu tree
Date: Wed, 13 Jan 2021 09:03:56 +1100 [thread overview]
Message-ID: <20210113090356.3ef1b139@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi all,
Commits
32678deac9cd ("timer: Report ignored local enqueue in nohz mode")
8beeef08bd76 ("entry: Report local wake up on resched blind zone while resuming to user")
7b3f45a1ad1f ("sched: Report local wake up on resched blind zone within idle loop")
4d19f38bb06c ("entry: Explicitly flush pending rcuog wakeup before last rescheduling points")
a5b60c670b22 ("rcu/nocb: Trigger self-IPI on late deferred wake up before user resume")
679a2750284c ("rcu/nocb: Perform deferred wake up before last idle's need_resched() check")
785ff6abc514 ("rcu: Pull deferred rcuog wake up to rcu_eqs_enter() callers")
d32f638a57e4 ("rcu: Remove superfluous rdp fetch")
97e90370b8f3 ("rcu/nocb: Detect unsafe checks for offloaded rdp")
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:[~2021-01-12 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:03 Stephen Rothwell [this message]
2021-01-13 0:19 ` linux-next: Signed-off-by missing for commits in the rcu tree Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 4:18 Stephen Rothwell
2021-06-25 14:18 ` Paul E. McKenney
2020-06-20 22:06 Stephen Rothwell
2020-06-21 15:53 ` Paul E. McKenney
2020-05-14 22:43 Stephen Rothwell
2020-05-14 23:01 ` Paul E. McKenney
2020-05-16 17:05 ` 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=20210113090356.3ef1b139@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).