From: "Paul E. McKenney" <paulmck@kernel.org>
To: Lihao Liang <lihaoliang@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: Update comment from rsp->rcu_gp_seq to rsp->gp_seq
Date: Thu, 14 May 2020 15:43:44 -0700 [thread overview]
Message-ID: <20200514224344.GX2869@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200514203434.22274-1-lihaoliang@google.com>
On Thu, May 14, 2020 at 09:34:34PM +0100, Lihao Liang wrote:
> Signed-off-by: Lihao Liang <lihaoliang@google.com>
Good eyes!!! Applied, thank you!
Thanx, Paul
> ---
> kernel/rcu/tree.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/rcu/tree.h b/kernel/rcu/tree.h
> index 2d7fcb9bdd34..508c46421eb3 100644
> --- a/kernel/rcu/tree.h
> +++ b/kernel/rcu/tree.h
> @@ -41,7 +41,7 @@ struct rcu_node {
> raw_spinlock_t __private lock; /* Root rcu_node's lock protects */
> /* some rcu_state fields as well as */
> /* following. */
> - unsigned long gp_seq; /* Track rsp->rcu_gp_seq. */
> + unsigned long gp_seq; /* Track rsp->gp_seq. */
> unsigned long gp_seq_needed; /* Track furthest future GP request. */
> unsigned long completedqs; /* All QSes done for this node. */
> unsigned long qsmask; /* CPUs or groups that need to switch in */
> @@ -149,7 +149,7 @@ union rcu_noqs {
> /* Per-CPU data for read-copy update. */
> struct rcu_data {
> /* 1) quiescent-state and grace-period handling : */
> - unsigned long gp_seq; /* Track rsp->rcu_gp_seq counter. */
> + unsigned long gp_seq; /* Track rsp->gp_seq counter. */
> unsigned long gp_seq_needed; /* Track furthest future GP request. */
> union rcu_noqs cpu_no_qs; /* No QSes yet for this CPU. */
> bool core_needs_qs; /* Core waits for quiesc state. */
> --
> 2.26.2.761.g0e0b3e54be-goog
>
prev parent reply other threads:[~2020-05-14 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 20:34 [PATCH] doc: Update comment from rsp->rcu_gp_seq to rsp->gp_seq Lihao Liang
2020-05-14 22:43 ` Paul E. McKenney [this message]
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=20200514224344.GX2869@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=lihaoliang@google.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox