mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Shile Zhang <shile.zhang@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include/linux: fix some typos
Date: Wed, 18 Mar 2020 09:04:09 -0700	[thread overview]
Message-ID: <20200318160409.GS3199@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200318114837.159978-1-shile.zhang@linux.alibaba.com>

On Wed, Mar 18, 2020 at 07:48:37PM +0800, Shile Zhang wrote:
> s/Not/Note/
> 
> Signed-off-by: Shile Zhang <shile.zhang@linux.alibaba.com>

Reviewed-by: Paul E. McKenney <paulmck@kernel.org>

Or I can take it if no one else wants it.  ;-)

							Thanx, Paul

> ---
>  include/linux/list_nulls.h | 4 ++--
>  include/linux/once.h       | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/include/linux/list_nulls.h b/include/linux/list_nulls.h
> index fa6e8471bd22..c845761fe5de 100644
> --- a/include/linux/list_nulls.h
> +++ b/include/linux/list_nulls.h
> @@ -60,7 +60,7 @@ static inline unsigned long get_nulls_value(const struct hlist_nulls_node *ptr)
>   * hlist_nulls_unhashed - Has node been removed and reinitialized?
>   * @h: Node to be checked
>   *
> - * Not that not all removal functions will leave a node in unhashed state.
> + * Note that not all removal functions will leave a node in unhashed state.
>   * For example, hlist_del_init_rcu() leaves the node in unhashed state,
>   * but hlist_nulls_del() does not.
>   */
> @@ -73,7 +73,7 @@ static inline int hlist_nulls_unhashed(const struct hlist_nulls_node *h)
>   * hlist_nulls_unhashed_lockless - Has node been removed and reinitialized?
>   * @h: Node to be checked
>   *
> - * Not that not all removal functions will leave a node in unhashed state.
> + * Note that not all removal functions will leave a node in unhashed state.
>   * For example, hlist_del_init_rcu() leaves the node in unhashed state,
>   * but hlist_nulls_del() does not.  Unlike hlist_nulls_unhashed(), this
>   * function may be used locklessly.
> diff --git a/include/linux/once.h b/include/linux/once.h
> index 9225ee6d96c7..095c6debd63b 100644
> --- a/include/linux/once.h
> +++ b/include/linux/once.h
> @@ -16,7 +16,7 @@ void __do_once_done(bool *done, struct static_key_true *once_key,
>   * out the condition into a nop. DO_ONCE() guarantees type safety of
>   * arguments!
>   *
> - * Not that the following is not equivalent ...
> + * Note that the following is not equivalent ...
>   *
>   *   DO_ONCE(func, arg);
>   *   DO_ONCE(func, arg);
> -- 
> 2.24.0.rc2
> 

      reply	other threads:[~2020-03-18 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 11:48 Shile Zhang
2020-03-18 16:04 ` 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=20200318160409.GS3199@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shile.zhang@linux.alibaba.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®