linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Ziwei Dai <ziwei.dai@unisoc.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the rcu tree
Date: Thu, 6 Apr 2023 08:36:19 +1000	[thread overview]
Message-ID: <20230406083619.65dee33a@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 499 bytes --]

Hi all,

In commit

  acdc79917d65 ("rcu/kvfree: Avoid freeing new kfree_rcu() memory after old grace period")

Fixes tag

  Fixes: 0392bebebf26 ("rcu/kvfree: Avoid freeing new kfree_rcu() memory after old grace period")

has these problem(s):

  - Subject does not match target commit subject
    Just use
	git log -1 --format='Fixes: %h ("%s")'

Maybe you meant:

Fixes: 0392bebebf26 ("rcu: Add multiple in-flight batches of kfree_rcu() work")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-04-05 22:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 22:36 Stephen Rothwell [this message]
2023-04-05 22:59 ` linux-next: Fixes tag needs some work in the rcu tree Paul E. McKenney
2023-04-06  1:42   ` 答复: " 代子为 (Ziwei Dai)
  -- strict thread matches above, loose matches on Subject: below --
2024-04-08 23:14 Stephen Rothwell
2024-04-03 21:39 Stephen Rothwell
2024-04-04 12:14 ` Uladzislau Rezki
2024-04-04 14:35   ` Paul E. McKenney
2024-04-05 17:17     ` Uladzislau Rezki
2024-04-01 21:03 Stephen Rothwell
2020-10-05 11:53 Stephen Rothwell
2020-10-05 14:07 ` Paul E. McKenney
2020-02-12 22:26 Stephen Rothwell
2020-02-13 10:35 ` Paul E. McKenney
2019-12-11 20:44 Stephen Rothwell
2019-12-11 22:52 ` Paul E. McKenney
     [not found] <20191029075041.7bf3f723@canb.auug.org.au>
2019-10-28 21:01 ` Stephen Rothwell
2019-10-29  0:36   ` Paul E. McKenney
2019-10-28 20:48 Stephen Rothwell

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=20230406083619.65dee33a@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 \
    --cc=ziwei.dai@unisoc.com \
    /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).