From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Vyshnav Ajith <puthen1977@gmail.com>,
paulmck@kernel.org, frederic@kernel.org,
neeraj.upadhyay@kernel.org, joel@joelfernandes.org,
josh@joshtriplett.org, boqun.feng@gmail.com, urezki@gmail.com,
rostedt@goodmis.org, jiangshanlai@gmail.com,
qiang.zhang1211@gmail.com, corbet@lwn.net
Cc: rcu@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Fixing Spelling Mistake in rculist_nulls.rst
Date: Fri, 22 Nov 2024 09:28:46 -0500 [thread overview]
Message-ID: <452c869c-9ffa-4c34-834f-359b7ac6c2a8@efficios.com> (raw)
In-Reply-To: <20241121232118.13507-1-puthen1977@gmail.com>
On 2024-11-21 18:21, Vyshnav Ajith wrote:
> NUll is a special marker and not maker I believe. Fixing typo with this patch.
Please fix the capitalization typo in the commit message. It should read
"Null".
Thanks,
Mathieu
>
> Signed-off-by: Vyshnav Ajith <puthen1977@gmail.com>
> ---
> Documentation/RCU/rculist_nulls.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RCU/rculist_nulls.rst b/Documentation/RCU/rculist_nulls.rst
> index 21e40fcc08de..88bce14b3c37 100644
> --- a/Documentation/RCU/rculist_nulls.rst
> +++ b/Documentation/RCU/rculist_nulls.rst
> @@ -13,7 +13,7 @@ Please read the basics in listRCU.rst.
> Using 'nulls'
> =============
>
> -Using special makers (called 'nulls') is a convenient way
> +Using special markers (called 'nulls') is a convenient way
> to solve following problem.
>
> Without 'nulls', a typical RCU linked list managing objects which are
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2024-11-22 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 23:21 Fixing Spelling Mistake in rculist_nulls.rst Vyshnav Ajith
2024-11-22 14:28 ` Mathieu Desnoyers [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=452c869c-9ffa-4c34-834f-359b7ac6c2a8@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=puthen1977@gmail.com \
--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