From: Brian Cain <bcain@quicinc.com>
To: Jiang Jian <jiangjian@cdjrlc.com>
Cc: "ebiederm@xmission.com" <ebiederm@xmission.com>,
"nathan@kernel.org" <nathan@kernel.org>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"keescook@chromium.org" <keescook@chromium.org>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
"linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] hexagon: drop unexpected word 'a' in comments
Date: Thu, 23 Jun 2022 06:53:31 +0000 [thread overview]
Message-ID: <SN6PR02MB4205512B03E6C2367BCFB5AEB8B59@SN6PR02MB4205.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20220623065100.8268-1-jiangjian@cdjrlc.com>
> -----Original Message-----
> From: Jiang Jian <jiangjian@cdjrlc.com>
...
>
> there is an unexpected word 'a' in the comments that need to be dropped
>
> file - arch/hexagon/kernel/traps.c
> line - 262
>
> * Precise bus errors may be recoverable with a a retry,
>
> changed to:
>
> * Precise bus errors may be recoverable with a retry,
>
> Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>
> ---
> arch/hexagon/kernel/traps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/hexagon/kernel/traps.c b/arch/hexagon/kernel/traps.c
> index 6447763ce5a9..a1f1085887aa 100644
> --- a/arch/hexagon/kernel/traps.c
> +++ b/arch/hexagon/kernel/traps.c
> @@ -259,7 +259,7 @@ static void illegal_instruction(struct pt_regs *regs)
> }
>
> /*
> - * Precise bus errors may be recoverable with a a retry,
> + * Precise bus errors may be recoverable with a retry,
> * but for now, treat them as irrecoverable.
> */
> static void precise_bus_error(struct pt_regs *regs)
> --
> 2.17.1
Acked-by: Brian Cain <bcain@quicinc.com>
prev parent reply other threads:[~2022-06-23 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 6:51 [PATCH] hexagon: drop unexpected word 'a' in comments Jiang Jian
2022-06-23 6:53 ` Brian Cain [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=SN6PR02MB4205512B03E6C2367BCFB5AEB8B59@SN6PR02MB4205.namprd02.prod.outlook.com \
--to=bcain@quicinc.com \
--cc=ebiederm@xmission.com \
--cc=jiangjian@cdjrlc.com \
--cc=keescook@chromium.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).