rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@linux.alibaba.com>
To: paulmck@kernel.org, josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	joel@joelfernandes.org, trivial@kernel.org
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
	Wei Yang <richard.weiyang@linux.alibaba.com>
Subject: [PATCH 0/4] rcu: trivial adjust for comments
Date: Fri, 12 Jun 2020 10:07:51 +0800	[thread overview]
Message-ID: <20200612020755.50526-1-richard.weiyang@linux.alibaba.com> (raw)

During code reading, I found there are several mismatch between comments
and code implementation.

Adjust the comment for better understanding.

Wei Yang (4):
  rcu: gp_max is protected by root rcu_node's lock
  rcu: grplo/grphi just records CPU number
  rcu: grpnum just records group number
  rcu: use gp_seq instead of rcu_gp_seq for consistency

 kernel/rcu/tree.h | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

-- 
2.20.1 (Apple Git-117)


             reply	other threads:[~2020-06-12  2:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12  2:07 Wei Yang [this message]
2020-06-12  2:07 ` [PATCH 1/4] rcu: gp_max is protected by root rcu_node's lock Wei Yang
2020-06-12  2:07 ` [PATCH 2/4] rcu: grplo/grphi just records CPU number Wei Yang
2020-06-12  2:07 ` [PATCH 3/4] rcu: grpnum just records group number Wei Yang
2020-06-12  2:07 ` [PATCH 4/4] rcu: use gp_seq instead of rcu_gp_seq for consistency Wei Yang
2020-06-12 14:12   ` Paul E. McKenney
2020-06-12 22:10     ` Wei Yang
2020-06-12 23:17       ` Paul E. McKenney

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=20200612020755.50526-1-richard.weiyang@linux.alibaba.com \
    --to=richard.weiyang@linux.alibaba.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=trivial@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;
as well as URLs for NNTP newsgroup(s).