public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jason Wang <wangborong@cdjrlc.com>
Cc: rdunlap@infradead.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fix typo in a comment
Date: Tue, 14 Dec 2021 10:31:11 +0100	[thread overview]
Message-ID: <20211214093111.GA7220@alpha.franken.de> (raw)
In-Reply-To: <20211211085132.224082-1-wangborong@cdjrlc.com>

On Sat, Dec 11, 2021 at 04:51:32PM +0800, Jason Wang wrote:
> The double `the' in the comment in line 344 is repeated. Remove one
> of them from the comment.
> 
> Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
> ---
>  arch/mips/mm/c-octeon.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mips/mm/c-octeon.c b/arch/mips/mm/c-octeon.c
> index 490322b01f91..737870d8fd94 100644
> --- a/arch/mips/mm/c-octeon.c
> +++ b/arch/mips/mm/c-octeon.c
> @@ -341,7 +341,7 @@ asmlinkage void cache_parity_error_octeon_recoverable(void)
>  }
>  
>  /*
> - * Called when the the exception is not recoverable
> + * Called when the exception is not recoverable
>   */
>  
>  asmlinkage void cache_parity_error_octeon_non_recoverable(void)
> -- 
> 2.34.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 ]

  reply	other threads:[~2021-12-14  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11  8:51 [PATCH] MIPS: Fix typo in a comment Jason Wang
2021-12-14  9:31 ` Thomas Bogendoerfer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-11  8:57 [PATCH] MIPS: fix " Jason Wang
2021-12-14  9:31 ` Thomas Bogendoerfer

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=20211214093111.GA7220@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=wangborong@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