[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220912134110.GD9232@alpha.franken.de>
Date: Mon, 12 Sep 2022 15:41:10 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Jason Wang <wangborong@...rlc.com>
Cc: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: Fix comment typo
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@...rlc.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 ]
Powered by blists - more mailing lists