[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Apr 2024 14:14:43 +0200
From: Uladzislau Rezki <urezki@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Paul E. McKenney" <paulmck@...nel.org>,
"Uladzislau Rezki (Sony)" <urezki@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the rcu tree
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.
--
Uladzislau Rezki
Powered by blists - more mailing lists