linux-kernel - Re: [PATCH] Fix a typo in Documentation/edac.txt.

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: <20150617204025.GC16999@pd.tnic>
Date:	Wed, 17 Jun 2015 22:40:25 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Rami Rosen <ramirose@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
	mchehab@....samsung.com
Subject: Re: [PATCH] Fix a typo in Documentation/edac.txt.

On Wed, Jun 17, 2015 at 11:16:19PM +0300, Rami Rosen wrote:
> This patch Fixes a typo in Documentation/edac.txt.
> 
> Signed-off-by: Rami Rosen <ramirose@...il.com>
> ---
>  Documentation/edac.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/edac.txt b/Documentation/edac.txt
> index 73fff13..9679433 100644
> --- a/Documentation/edac.txt
> +++ b/Documentation/edac.txt
> @@ -664,7 +664,7 @@ exports one
>  
>     Each QPI is exported as a different memory controller.
>  
> -2) Nehalem MC has the hability to generate errors. The driver implements this
> +2) Nehalem MC has the ability to generate errors. The driver implements this
>     functionality via some error injection nodes:
>  
>     For injecting a memory error, there are some sysfs nodes, under

I see at least one more typo in that file, care to go through it with
the magnifying glass and fix them all?

:-)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/