From: Dimitri Sivanich <sivanich@hpe.com>
To: Jiang Jian <jiangjian@cdjrlc.com>
Cc: dimitri.sivanich@hpe.com, arnd@arndb.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: sgi-gru: grukservices: drop unexpected word "the" in the comments
Date: Tue, 21 Jun 2022 14:18:33 -0500 [thread overview]
Message-ID: <20220621191833.GA31015@hpe.com> (raw)
In-Reply-To: <20220621123203.118488-1-jiangjian@cdjrlc.com>
Acked-by: Dimitri Sivanich <sivanich@hpe.com>
On Tue, Jun 21, 2022 at 08:32:03PM +0800, Jiang Jian wrote:
> there is an unexpected word "the" in the comments that need to be dropped
> file: drivers/misc/sgi-gru/grukservices.c
> line: 39
> * reserved whenever the the kernel context for the blade is loaded. Note
> changed to
> * reserved whenever the kernel context for the blade is loaded. Note
>
> Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>
> ---
> drivers/misc/sgi-gru/grukservices.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/misc/sgi-gru/grukservices.c b/drivers/misc/sgi-gru/grukservices.c
> index 19dbdad8ad8a..fa1f5a632e7f 100644
> --- a/drivers/misc/sgi-gru/grukservices.c
> +++ b/drivers/misc/sgi-gru/grukservices.c
> @@ -36,7 +36,7 @@
> * kernel/user requirements.
> *
> * Blade percpu resources reserved for kernel use. These resources are
> - * reserved whenever the the kernel context for the blade is loaded. Note
> + * reserved whenever the kernel context for the blade is loaded. Note
> * that the kernel context is not guaranteed to be always available. It is
> * loaded on demand & can be stolen by a user if the user demand exceeds the
> * kernel demand. The kernel can always reload the kernel context but
> --
> 2.17.1
prev parent reply other threads:[~2022-06-21 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 12:32 [PATCH] misc: sgi-gru: grukservices: drop unexpected word "the" in the comments Jiang Jian
2022-06-21 19:18 ` Dimitri Sivanich [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=20220621191833.GA31015@hpe.com \
--to=sivanich@hpe.com \
--cc=arnd@arndb.de \
--cc=dimitri.sivanich@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiangjian@cdjrlc.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox