From: "Paul E. McKenney" <paulmck@kernel.org>
To: Lin Yu Chen <starpt.official@gmail.com>
Cc: corbet@lwn.net, frederic@kernel.org, quic_neeraju@quicinc.com,
josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
joel@joelfernandes.org, rcu@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Fix typo in Documentation/RCU/checklist.rst
Date: Tue, 11 Apr 2023 21:52:19 -0700 [thread overview]
Message-ID: <ddef7eae-6fd4-4a79-881f-e99fbed48d67@paulmck-laptop> (raw)
In-Reply-To: <20230411141341.74133-1-starpt.official@gmail.com>
On Tue, Apr 11, 2023 at 07:13:41AM -0700, Lin Yu Chen wrote:
> This commit corrects the spelling of "not" to "note" to accurately
> convey the intended meaning.
>
> Signed-off-by: Lin Yu Chen <starpt.official@gmail.com>
Good eyes, thank you!
However, Qiuxu Zhuo beat you to this one, please see this commit
in the -rcu tree:
e5ad8b68f8d4 ("Documentation/RCU: s/not/note/ in checklist.rst")
Thanx, Paul
> ---
> Documentation/RCU/checklist.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RCU/checklist.rst b/Documentation/RCU/checklist.rst
> index cc361fb01ed4..bd3c58c44bef 100644
> --- a/Documentation/RCU/checklist.rst
> +++ b/Documentation/RCU/checklist.rst
> @@ -70,7 +70,7 @@ over a rather long period of time, but improvements are always welcome!
> can serve as rcu_read_lock_sched(), but is less readable and
> prevents lockdep from detecting locking issues.
>
> - Please not that you *cannot* rely on code known to be built
> + Please note that you *cannot* rely on code known to be built
> only in non-preemptible kernels. Such code can and will break,
> especially in kernels built with CONFIG_PREEMPT_COUNT=y.
>
> --
> 2.25.1
>
prev parent reply other threads:[~2023-04-12 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 14:13 Lin Yu Chen
2023-04-12 4:52 ` 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=ddef7eae-6fd4-4a79-881f-e99fbed48d67@paulmck-laptop \
--to=paulmck@kernel.org \
--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=mathieu.desnoyers@efficios.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=starpt.official@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®