From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Peter Zijlstra <peterz@infradead.org>,
Silvio Fricke <silvio.fricke@gmail.com>,
linux-doc@vger.kernel.org, Ming Lei <ming.lei@canonical.com>,
"Luis R . Rodriguez" <mcgrof@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup
Date: Mon, 28 Nov 2016 07:29:08 -0700 [thread overview]
Message-ID: <20161128072908.2472f347@lwn.net> (raw)
In-Reply-To: <20161128141314.o6favw3o6eo3weww@phenom.ffwll.local>
On Mon, 28 Nov 2016 15:13:14 +0100
Daniel Vetter <daniel@ffwll.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
next prev parent reply other threads:[~2016-11-28 14:29 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 12:42 [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-24 12:42 ` [PATCH 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-24 12:42 ` [PATCH 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-24 19:46 ` [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Mauro Carvalho Chehab
2016-11-25 10:02 ` [PATCH v2 " Silvio Fricke
2016-11-25 10:02 ` [PATCH v2 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 13:03 ` Mauro Carvalho Chehab
2016-11-25 10:02 ` [PATCH v2 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 13:25 ` Mauro Carvalho Chehab
2016-11-25 10:02 ` [PATCH v2 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 13:34 ` Mauro Carvalho Chehab
2016-11-25 13:47 ` S. Fricke
2016-11-25 13:58 ` Mauro Carvalho Chehab
2016-11-25 10:02 ` [PATCH v2 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 13:34 ` Mauro Carvalho Chehab
2016-11-25 14:59 ` [PATCH v3 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-25 14:59 ` [PATCH v3 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 20:53 ` Mauro Carvalho Chehab
2016-11-25 14:59 ` [PATCH v3 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 21:01 ` Mauro Carvalho Chehab
2016-11-25 21:58 ` Peter Zijlstra
2016-11-27 14:53 ` S. Fricke
2016-11-27 18:36 ` Jani Nikula
2016-11-27 23:59 ` Jonathan Corbet
2016-11-28 7:26 ` Peter Zijlstra
2016-11-28 8:44 ` Daniel Vetter
2016-11-28 10:20 ` Peter Zijlstra
2016-11-28 11:08 ` Mauro Carvalho Chehab
2016-11-28 11:54 ` Peter Zijlstra
2016-11-28 13:46 ` Daniel Vetter
2016-11-28 15:14 ` Mauro Carvalho Chehab
2016-11-28 11:16 ` Jani Nikula
2016-11-28 11:56 ` Peter Zijlstra
2016-11-28 12:32 ` Jani Nikula
2016-11-28 14:13 ` Daniel Vetter
2016-11-28 14:29 ` Jonathan Corbet [this message]
2016-11-25 14:59 ` [PATCH v3 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 21:10 ` Mauro Carvalho Chehab
2016-11-25 14:59 ` [PATCH v3 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 20:50 ` Mauro Carvalho Chehab
2016-12-01 16:11 ` Luis R. Rodriguez
2016-12-01 16:45 ` Greg Kroah-Hartman
2016-11-28 17:30 ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-28 17:30 ` [PATCH v4 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-28 17:30 ` [PATCH v4 2/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-28 17:30 ` [PATCH v4 3/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-28 17:30 ` [PATCH v4 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-12-01 0:51 ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Jonathan Corbet
2016-12-01 15:49 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161128072908.2472f347@lwn.net \
--to=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mchehab@kernel.org \
--cc=ming.lei@canonical.com \
--cc=peterz@infradead.org \
--cc=silvio.fricke@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).