From: "Paul E. McKenney" <paulmck@kernel.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the rcu tree
Date: Thu, 4 Apr 2024 07:35:31 -0700 [thread overview]
Message-ID: <73bf08df-3edd-4948-bea1-3962063d673e@paulmck-laptop> (raw)
In-Reply-To: <Zg6Zs76UDYQsJTWM@pc636>
On Thu, Apr 04, 2024 at 02:14:43PM +0200, Uladzislau Rezki wrote:
> Hello!
>
> > Hi all,
> >
> > In commit
> >
> > a55be9aacc45 ("rcu: Do not release a wait-head from a GP kthread")
> >
> > Fixes tag
> >
> > Fixes: 05a10b921000 ("rcu: Support direct wake-up of synchronize_rcu() users")
> >
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: 654f59c6bc95 ("rcu: Support direct wake-up of synchronize_rcu() users")
> >
> I have a question. Could you please clarify why those commits are in the linux-next?
> Those commits have to go over RCU tree. It looks like i am missing something but
> please elaborate.
Stephen pulls the -rcu "rcu/next" tag into -next, and does similarly for
a large number of other trees. This serves to pre-test the commits that
are likely to show up in the upcoming merge window. The pre-testing
includes the build testing that Stephen does directly and additional
testing that others do on the -next tree (for example, I occasionally
run rcutorture on it).
So these commits are in -next because I told Stephen to include them.
But if you would like, I would be happy to pull your series out of the
portion covered by rcu/next for the time being.
Thanx, Paul
next prev parent reply other threads:[~2024-04-04 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 21:39 linux-next: Fixes tag needs some work in the rcu tree Stephen Rothwell
2024-04-04 12:14 ` Uladzislau Rezki
2024-04-04 14:35 ` Paul E. McKenney [this message]
2024-04-05 17:17 ` Uladzislau Rezki
-- strict thread matches above, loose matches on Subject: below --
2024-04-08 23:14 Stephen Rothwell
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
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=73bf08df-3edd-4948-bea1-3962063d673e@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=urezki@gmail.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).