From: Stafford Horne <shorne@gmail.com>
To: Xiang wangx <wangxiang@cdjrlc.com>
Cc: jonas@southpole.se, openrisc@lists.librecores.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] openrisc: Fix syntax errors in comments
Date: Tue, 28 Jun 2022 09:37:46 +0900 [thread overview]
Message-ID: <YrpNWjLqHZrcrhl6@antec> (raw)
In-Reply-To: <20220602085350.12741-1-wangxiang@cdjrlc.com>
On Thu, Jun 02, 2022 at 04:53:50PM +0800, Xiang wangx wrote:
> Delete the redundant word 'the'.
>
> Signed-off-by: Xiang wangx <wangxiang@cdjrlc.com>
> ---
> arch/openrisc/kernel/unwinder.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/openrisc/kernel/unwinder.c b/arch/openrisc/kernel/unwinder.c
> index 8ae15c2c1845..c6ad6f867a6a 100644
> --- a/arch/openrisc/kernel/unwinder.c
> +++ b/arch/openrisc/kernel/unwinder.c
> @@ -25,7 +25,7 @@ struct or1k_frameinfo {
> /*
> * Verify a frameinfo structure. The return address should be a valid text
> * address. The frame pointer may be null if its the last frame, otherwise
> - * the frame pointer should point to a location in the stack after the the
> + * the frame pointer should point to a location in the stack after the
> * top of the next frame up.
> */
> static inline int or1k_frameinfo_valid(struct or1k_frameinfo *frameinfo)
> --
> 2.36.1
This looks good to me, I will queue with 5.19 fixes.
-Stafford
prev parent reply other threads:[~2022-06-28 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 8:53 [PATCH] openrisc: Fix syntax errors in comments Xiang wangx
2022-06-28 0:37 ` Stafford Horne [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=YrpNWjLqHZrcrhl6@antec \
--to=shorne@gmail.com \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=wangxiang@cdjrlc.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).