From: Frederic Weisbecker <frederic@kernel.org>
To: neeraj.upadhyay@kernel.org
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
paulmck@kernel.org, joelagnelf@nvidia.com, boqun.feng@gmail.com,
urezki@gmail.com, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
qiang.zhang1211@gmail.com, neeraj.iitr10@gmail.com,
neeraj.upadhyay@amd.com
Subject: Re: [PATCH rcu 4/5] Documentation/kernel-parameters: Update rcu_normal_wake_from_gp doc
Date: Wed, 9 Jul 2025 13:37:21 +0200 [thread overview]
Message-ID: <aG5UcXSbQf2RqZNk@localhost.localdomain> (raw)
In-Reply-To: <20250709104118.15532-5-neeraj.upadhyay@kernel.org>
Le Wed, Jul 09, 2025 at 04:11:17PM +0530, neeraj.upadhyay@kernel.org a écrit :
> From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
>
> Update the documentation about rcu_normal_wake_from_gp parameter.
>
> Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> Signed-off-by: Neeraj Upadhyay (AMD) <neeraj.upadhyay@kernel.org>
Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2025-07-09 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 10:41 [PATCH rcu 0/5] RCU changes for v6.17 neeraj.upadhyay
2025-07-09 10:41 ` [PATCH rcu 1/5] rcu: Robustify rcu_is_cpu_rrupt_from_idle() neeraj.upadhyay
2025-07-09 10:41 ` [PATCH rcu 2/5] rcu: Protect ->defer_qs_iw_pending from data race neeraj.upadhyay
2025-07-09 11:27 ` Frederic Weisbecker
2025-07-09 10:41 ` [PATCH rcu 3/5] rcu: Enable rcu_normal_wake_from_gp on small systems neeraj.upadhyay
2025-07-09 11:36 ` Frederic Weisbecker
2025-07-09 10:41 ` [PATCH rcu 4/5] Documentation/kernel-parameters: Update rcu_normal_wake_from_gp doc neeraj.upadhyay
2025-07-09 11:37 ` Frederic Weisbecker [this message]
2025-07-09 10:41 ` [PATCH rcu 5/5] rcu: Fix rcu_read_unlock() deadloop due to IRQ work neeraj.upadhyay
2025-07-09 12:48 ` Frederic Weisbecker
2025-07-10 19:41 ` Joel Fernandes
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=aG5UcXSbQf2RqZNk@localhost.localdomain \
--to=frederic@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.iitr10@gmail.com \
--cc=neeraj.upadhyay@amd.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®