From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kbuild test robot <lkp@intel.com>
Subject: linux-next: Fixes tag needs some work in the rcu tree
Date: Thu, 12 Dec 2019 07:44:51 +1100 [thread overview]
Message-ID: <20191212074451.18c69a64@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
Hi all,
In commit
3b570f534011 ("rcutorture: The rcu_boot_ended variable can be static")
Fixes tag
Fixes: 68ce6668914d ("rcutorture: Suppress forward-progress complaints during early boot")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: 7e1204f7a29e ("rcutorture: Suppress forward-progress complaints during early boot")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-12-11 20:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 20:44 Stephen Rothwell [this message]
2019-12-11 22:52 ` linux-next: Fixes tag needs some work in the rcu tree Paul E. McKenney
-- 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
2023-04-05 22:36 Stephen Rothwell
2023-04-05 22:59 ` Paul E. McKenney
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
[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=20191212074451.18c69a64@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.