From: Frederic Weisbecker <frederic@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>, rcu <rcu@vger.kernel.org>,
Cheng-Jui Wang <Cheng-Jui.Wang@mediatek.com>
Subject: Re: [PATCH 0/3] rcu/nocb updates
Date: Fri, 13 Sep 2024 23:44:23 +0200 [thread overview]
Message-ID: <ZuSyN_1jKUrVAprO@pavilion.home> (raw)
In-Reply-To: <20240913214205.12359-1-frederic@kernel.org>
Le Fri, Sep 13, 2024 at 11:42:02PM +0200, Frederic Weisbecker a écrit :
> Hi,
>
> This series include:
>
> * Fix another RT wake up while CPU is offline (reported by Cheng-Jui Wang)
> * Cleanup rcuo wakeup
> * Remove another superfluous barrier
>
> Thanks.
>
> Frederic Weisbecker (3):
> rcu/nocb: Fix RT throttling hrtimer armed from offline CPU
> rcu/nocb: Conditionally wake up rcuo if not already waiting on GP
> rcu/nocb: Remove superfluous memory barrier after bypass enqueue
>
> kernel/rcu/tree_nocb.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Please discard this series. It has been applied already. Scripting error...
next prev parent reply other threads:[~2024-09-13 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 21:42 [PATCH 0/3] rcu/nocb updates Frederic Weisbecker
2024-09-13 21:42 ` [PATCH 1/3] rcu/nocb: Fix RT throttling hrtimer armed from offline CPU Frederic Weisbecker
2024-09-13 21:42 ` [PATCH 2/3] rcu/nocb: Conditionally wake up rcuo if not already waiting on GP Frederic Weisbecker
2024-09-13 21:42 ` [PATCH 3/3] rcu/nocb: Remove superfluous memory barrier after bypass enqueue Frederic Weisbecker
2024-09-13 21:44 ` Frederic Weisbecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-13 22:56 [PATCH 0/3] rcu/nocb updates Frederic Weisbecker
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=ZuSyN_1jKUrVAprO@pavilion.home \
--to=frederic@kernel.org \
--cc=Cheng-Jui.Wang@mediatek.com \
--cc=boqun.feng@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@amd.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--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