[PATCH] EDAC/sb_edac: Fix typos

[PATCH] EDAC/sb_edac: Fix typos

[Andrew Kreimer]

Fix typos in comments.

Reported-by: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Andrew Kreimer <algonell@gmail.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

RE: [PATCH] EDAC/sb_edac: Fix typos

[Zhuo, Qiuxu]

> From: Andrew Kreimer <algonell@gmail.com>
> [...]
> Subject: [PATCH] EDAC/sb_edac: Fix typos
> 
> Fix typos in comments.
> 
> Reported-by: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Andrew Kreimer <algonell@gmail.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@intel.com>

Thanks!
-Qiuxu