linux-kernel - Re: [PATCH] MIPS: Octeon: fix typo in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20220523091628.GB5069@alpha.franken.de>
Date:   Mon, 23 May 2022 11:16:28 +0200
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Julia Lawall <Julia.Lawall@...ia.fr>
Cc:     kernel-janitors@...r.kernel.org, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: Octeon: fix typo in comment

On Sat, May 21, 2022 at 01:11:15PM +0200, Julia Lawall wrote:
> Spelling mistake (triple letters) in comment.
> Detected with the help of Coccinelle.
> 
> Signed-off-by: Julia Lawall <Julia.Lawall@...ia.fr>
> 
> ---
>  arch/mips/pci/pcie-octeon.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mips/pci/pcie-octeon.c b/arch/mips/pci/pcie-octeon.c
> index 50a3394a9d25..c9edd3fb380d 100644
> --- a/arch/mips/pci/pcie-octeon.c
> +++ b/arch/mips/pci/pcie-octeon.c
> @@ -895,7 +895,7 @@ static int __cvmx_pcie_rc_initialize_gen1(int pcie_port)
>  	mem_access_subid.s.nsw = 0;	/* Enable Snoop for Writes. */
>  	mem_access_subid.s.ror = 0;	/* Disable Relaxed Ordering for Reads. */
>  	mem_access_subid.s.row = 0;	/* Disable Relaxed Ordering for Writes. */
> -	mem_access_subid.s.ba = 0;	/* PCIe Adddress Bits <63:34>. */
> +	mem_access_subid.s.ba = 0;	/* PCIe Address Bits <63:34>. */
>  
>  	/*
>  	 * Setup mem access 12-15 for port 0, 16-19 for port 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 ]