From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: SeongJae Park <sj@kernel.org>,
joel@joelfernandes.org, mmpgouride@gmail.com, corbet@lwn.net,
rcu@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] Docs/RCU/rculist_nulls: Minor fixup
Date: Thu, 15 Jun 2023 18:10:01 +0000 [thread overview]
Message-ID: <20230615181004.86850-1-sj@kernel.org> (raw)
Changes from v2
(https://lore.kernel.org/rcu/20230613182434.88317-1-sj@kernel.org/)
- Drop first two patches that merged to Paul's tree
- Add definition of 'obj' (Paul E. McKenney)
- Fix more wrong hlist_[nulls]_head field name mentions
Changes from v1
(https://lore.kernel.org/rcu/20230518224008.2468-1-sj@kernel.org/)
- Add Reviewed-by tags from Joel Fernandes for first three patches
- Fix the text for wrong extra _release()
---
Fix minor problems in example code snippets and the text of
rculist_nulls.rst file.
SeongJae Park (3):
Docs/RCU/rculist_nulls: Specify type of the object in examples
Docs/RCU/rculist_nulls: Fix hlist_[nulls]_head field names of 'obj'
Docs/RCU/rculist_nulls: Fix text about atomic_set_release()
Documentation/RCU/rculist_nulls.rst | 28 +++++++++++++++++++++-------
1 file changed, 21 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2023-06-15 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 18:10 SeongJae Park [this message]
2023-06-15 18:10 ` [PATCH v3 1/3] Docs/RCU/rculist_nulls: Specify type of the object in examples SeongJae Park
2023-06-16 17:46 ` Alan Huang
2023-06-16 18:54 ` SeongJae Park
2023-06-16 23:18 ` Paul E. McKenney
2023-06-15 18:10 ` [PATCH v3 2/3] Docs/RCU/rculist_nulls: Fix hlist_[nulls]_head field names of 'obj' SeongJae Park
2023-06-15 18:10 ` [PATCH v3 3/3] Docs/RCU/rculist_nulls: Fix text about atomic_set_release() SeongJae Park
2023-06-16 16:52 ` [PATCH v3 0/3] Docs/RCU/rculist_nulls: Minor fixup 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=20230615181004.86850-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=corbet@lwn.net \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmpgouride@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@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;
as well as URLs for NNTP newsgroup(s).