linux-kernel - Re: [PATCH] locking/lockdep: Revise Documentation/locking/crossrelease.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: <20171109002347.GA24935@X58A-UD3R>
Date:   Thu, 9 Nov 2017 09:23:47 +0900
From:   Byungchul Park <byungchul.park@....com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     peterz@...radead.org, tglx@...utronix.de,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        linux-block@...r.kernel.org, kernel-team@....com
Subject: Re: [PATCH] locking/lockdep: Revise
 Documentation/locking/crossrelease.txt

On Wed, Nov 08, 2017 at 10:34:38AM +0100, Ingo Molnar wrote:
> 
> * Byungchul Park <byungchul.park@....com> wrote:
> 
> > I'm afraid the revision is not perfect yet. Of course, the document can
> > have got much better english by others than me.
> > 
> > But,
> > 
> > I think I should enhance it as much as I can, before they can help it
> > starting with a better one.
> > 
> > In addition, I removed verboseness as much as possible.
> > 
> > ----->8-----
> > From c7795104ca6ac6dd9f7fd944aee23a2011a6d3a2 Mon Sep 17 00:00:00 2001
> > From: Byungchul Park <byungchul.park@....com>
> > Date: Mon, 30 Oct 2017 14:51:26 +0900
> > Subject: [PATCH] locking/lockdep: Revise
> >  Documentation/locking/crossrelease.txt
> > 
> > The document should've been written with a better readability. Revise it
> > to enhance its readability.
> > 
> > Signed-off-by: Byungchul Park <byungchul.park@....com>
> > ---
> >  Documentation/locking/crossrelease.txt | 388 +++++++++++++++------------------
> 
> Could you please run a spellchecker over this text? It's still full of typos and 
> various grammar mistakes...

Sure.. I have to.. I will look for a way and use it. Thanks a lot.

> Thanks,
> 
> 	Ingo