All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Mukesh Ojha <mojha@codeaurora.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: Fix spelling mistake "greate"->"great"
Date: Tue, 30 Jul 2019 09:02:21 -0700	[thread overview]
Message-ID: <20190730160221.GX14271@linux.ibm.com> (raw)
In-Reply-To: <1564386957-22833-1-git-send-email-mojha@codeaurora.org>

On Mon, Jul 29, 2019 at 01:25:57PM +0530, Mukesh Ojha wrote:
> There is a spelling mistake in file tree_exp.h,
> fix this.
> 
> Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>

Queued, thank you very much!

							Thanx, Paul

> ---
>  kernel/rcu/tree_exp.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/rcu/tree_exp.h b/kernel/rcu/tree_exp.h
> index af7e7b9..609fc87 100644
> --- a/kernel/rcu/tree_exp.h
> +++ b/kernel/rcu/tree_exp.h
> @@ -781,7 +781,7 @@ static int rcu_print_task_exp_stall(struct rcu_node *rnp)
>   * other hand, if the CPU is not in an RCU read-side critical section,
>   * the IPI handler reports the quiescent state immediately.
>   *
> - * Although this is a greate improvement over previous expedited
> + * Although this is a great improvement over previous expedited
>   * implementations, it is still unfriendly to real-time workloads, so is
>   * thus not recommended for any sort of common-case code.  In fact, if
>   * you are using synchronize_rcu_expedited() in a loop, please restructure
> -- 
> Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
> Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
> 


      reply	other threads:[~2019-07-30 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29  7:55 [PATCH] rcu: Fix spelling mistake "greate"->"great" Mukesh Ojha
2019-07-30 16:02 ` 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=20190730160221.GX14271@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mojha@codeaurora.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.