From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Shaomin Deng <dengshaomin@cdjrlc.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fix comments typo
Date: Mon, 12 Sep 2022 15:39:18 +0200 [thread overview]
Message-ID: <20220912133918.GA9232@alpha.franken.de> (raw)
In-Reply-To: <20220827154640.9687-1-dengshaomin@cdjrlc.com>
On Sat, Aug 27, 2022 at 11:46:40AM -0400, Shaomin Deng wrote:
> Remove the repeated word "as" in comments.
>
> Signed-off-by: Shaomin Deng <dengshaomin@cdjrlc.com>
> ---
> arch/mips/cavium-octeon/setup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/cavium-octeon/setup.c b/arch/mips/cavium-octeon/setup.c
> index 00bf269763cf..9ad12fb6a9a6 100644
> --- a/arch/mips/cavium-octeon/setup.c
> +++ b/arch/mips/cavium-octeon/setup.c
> @@ -527,7 +527,7 @@ void octeon_user_io_init(void)
> /* Get the current settings for CP0_CVMMEMCTL_REG */
> cvmmemctl.u64 = read_c0_cvmmemctl();
> /* R/W If set, marked write-buffer entries time out the same
> - * as as other entries; if clear, marked write-buffer entries
> + * as other entries; if clear, marked write-buffer entries
> * use the maximum timeout. */
> cvmmemctl.s.dismarkwblongto = 1;
> /* R/W If set, a merged store does not clear the write-buffer
> --
> 2.35.1
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-09-12 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 15:46 [PATCH] MIPS: Fix comments typo Shaomin Deng
2022-09-12 13:39 ` Thomas Bogendoerfer [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=20220912133918.GA9232@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=dengshaomin@cdjrlc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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