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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 28 Nov 2016 07:29:08 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Daniel Vetter <daniel@...ll.ch>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Silvio Fricke <silvio.fricke@...il.com>,
        linux-doc@...r.kernel.org, Ming Lei <ming.lei@...onical.com>,
        "Luis R . Rodriguez" <mcgrof@...nel.org>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        linux-kernel@...r.kernel.org,
        Jani Nikula <jani.nikula@...ux.intel.com>
Subject: Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST
 markup

On Mon, 28 Nov 2016 15:13:14 +0100
Daniel Vetter <daniel@...ll.ch> wrote:

> Jon, should we document that we want a very light-handed approach to rst
> markup in kernel docs? This has come up a few times now, and irrespective
> of what exactly we're going to do with atomic_ops.txt I think it would
> help with making txt->rst conversions palatable to the core kernel
> community. And it's knida my own preference too ...

I think that makes sense, yes.  We just have to decide what a
light-handed approach actually is...

jon

Powered by blists - more mailing lists