linux-kernel - RE: [PATCH] EDAC/sb

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: <CY8PR11MB7134987CFC664AE4F7DFA353899A2@CY8PR11MB7134.namprd11.prod.outlook.com>
Date: Tue, 10 Sep 2024 05:56:22 +0000
From: "Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>
To: Andrew Kreimer <algonell@...il.com>, "Luck, Tony" <tony.luck@...el.com>,
	Borislav Petkov <bp@...en8.de>, James Morse <james.morse@....com>, "Mauro
 Carvalho Chehab" <mchehab@...nel.org>, Robert Richter <rric@...nel.org>
CC: "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>, "Matthew
 Wilcox" <willy@...radead.org>
Subject: RE: [PATCH] EDAC/sb_edac: Fix typos

> From: Andrew Kreimer <algonell@...il.com>
> [...]
> Subject: [PATCH] EDAC/sb_edac: Fix typos
> 
> Fix typos in comments.
> 
> Reported-by: Matthew Wilcox <willy@...radead.org>
> Signed-off-by: Andrew Kreimer <algonell@...il.com>
> ---
>  drivers/edac/sb_edac.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/edac/sb_edac.c b/drivers/edac/sb_edac.c index
> d5f12219598a..d47f1240c738 100644
> --- a/drivers/edac/sb_edac.c
> +++ b/drivers/edac/sb_edac.c
> @@ -1797,7 +1797,7 @@ static void get_memory_layout(const struct
> mem_ctl_info *mci)
>  	 * Step 2) Get SAD range and SAD Interleave list
>  	 * TAD registers contain the interleave wayness. However, it
>  	 * seems simpler to just discover it indirectly, with the
> -	 * algorithm bellow.
> +	 * algorithm below.
>  	 */
>  	prv = 0;
>  	for (n_sads = 0; n_sads < pvt->info.max_sad; n_sads++) { @@ -2055,7
> +2055,7 @@ static int get_memory_error_data(struct mem_ctl_info *mci,
> 
>  	/*
>  	 * Step 0) Check if the address is at special memory ranges
> -	 * The check bellow is probably enough to fill all cases where
> +	 * The check below is probably enough to fill all cases where
>  	 * the error is not inside a memory, except for the legacy
>  	 * range (e. g. VGA addresses). It is unlikely, however, that the
>  	 * memory controller would generate an error on that range.
> --
> 2.46.0

Reviewed-by: Qiuxu Zhuo <qiuxu.zhuo@...el.com>

Thanks!
-Qiuxu