All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: Adrian Huang <adrianhuang0701@gmail.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	rcu@vger.kernel.org, Adrian Huang <ahuang12@lenovo.com>
Subject: Re: [PATCH 1/1] docs: RCU: typo fix
Date: Thu, 16 Mar 2023 15:18:20 +0000	[thread overview]
Message-ID: <20230316151820.GA373925@google.com> (raw)
In-Reply-To: <20230316070936.733-1-adrianhuang0701@gmail.com>

On Thu, Mar 16, 2023 at 03:09:36PM +0800, Adrian Huang wrote:
> From: Adrian Huang <ahuang12@lenovo.com>
> 
> It should be "Please note that ..." instead of "Please not that ...".
> 
> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>

Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>

thanks,

 - Joel

> ---
>  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.34.1
> 

  reply	other threads:[~2023-03-16 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  7:09 [PATCH 1/1] docs: RCU: typo fix Adrian Huang
2023-03-16 15:18 ` Joel Fernandes [this message]
2023-03-17  1:15 ` 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=20230316151820.GA373925@google.com \
    --to=joel@joelfernandes.org \
    --cc=adrianhuang0701@gmail.com \
    --cc=ahuang12@lenovo.com \
    --cc=corbet@lwn.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.