From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jason Wang <wangborong@cdjrlc.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fix comment typo
Date: Mon, 12 Sep 2022 15:41:10 +0200 [thread overview]
Message-ID: <20220912134110.GD9232@alpha.franken.de> (raw)
In-Reply-To: <20220811121450.24057-1-wangborong@cdjrlc.com>
On Thu, Aug 11, 2022 at 08:14:50PM +0800, Jason Wang wrote:
> The double `it' is duplicated in the comment, remove one.
>
> Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
> ---
> arch/mips/math-emu/cp1emu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/math-emu/cp1emu.c b/arch/mips/math-emu/cp1emu.c
> index 587cf1d115e8..265bc57819df 100644
> --- a/arch/mips/math-emu/cp1emu.c
> +++ b/arch/mips/math-emu/cp1emu.c
> @@ -1032,7 +1032,7 @@ static int cop1Emulate(struct pt_regs *xcp, struct mips_fpu_struct *ctx,
> */
> if (dec_insn.micro_mips_mode) {
> /*
> - * If next instruction is a 16-bit instruction, then it
> + * If next instruction is a 16-bit instruction, then
> * it cannot be a FPU instruction. This could happen
> * since we can be called for non-FPU instructions.
> */
> --
> 2.36.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 ]
next prev parent reply other threads:[~2022-09-12 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 12:14 [PATCH] MIPS: Fix comment typo Jason Wang
2022-09-12 13:41 ` Thomas Bogendoerfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-16 4:01 Jason Wang
2022-07-30 9:03 ` Thomas Bogendoerfer
2022-07-15 4:39 Jason Wang
2022-07-18 15:06 ` Sergey Shtylyov
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=20220912134110.GD9232@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.