linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the rcu tree
Date: Tue, 12 Jan 2021 16:19:59 -0800	[thread overview]
Message-ID: <20210113001959.GO2743@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20210113090356.3ef1b139@canb.auug.org.au>

On Wed, Jan 13, 2021 at 09:03:56AM +1100, Stephen Rothwell wrote:
> 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.

Thank you, fixed, and apologies for the hassle.

(This is what happens when "git am" doesn't like a patch series,
so I enlist git's help by pulling it from the author's tree to its
natural location, rebasing it, but then forgetting to manually add my
Signed-off-by...)

							Thanx, Paul

  reply	other threads:[~2021-01-13  0:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 22:03 linux-next: Signed-off-by missing for commits in the rcu tree Stephen Rothwell
2021-01-13  0:19 ` 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
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=20210113001959.GO2743@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;
as well as URLs for NNTP newsgroup(s).