From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jani Nikula <jani.nikula@intel.com>, Takashi Iwai <tiwai@suse.de>,
Markus Heiser <markus.heiser@darmarit.de>,
Silvio Fricke <silvio.fricke@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH 5/9] kernel-api.tmpl: convert it to ReST
Date: Fri, 31 Mar 2017 09:05:37 -0600 [thread overview]
Message-ID: <20170331090537.567730e8@lwn.net> (raw)
In-Reply-To: <0186e4eb40e09f92a7ec59f195d93af38176433f.1490904090.git.mchehab@s-opensource.com>
On Thu, 30 Mar 2017 17:11:32 -0300
Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> Brainless conversion of genericirq.tmpl book to ReST, via
> Documentation/sphinx/tmplcvt
This one kind of showcases why I'm nervous about bulk conversions. It's
a bit of a dumping-ground document, with a bit of everything, and I think
we can do better. And, in particular, this one contains a bunch of stuff
that belongs in the driver-api manual instead. So, at a minimum, I would
really like to see this template split across those two manuals.
If you promise me a followup patch doing that, maybe I can go ahead and
merge this series now :)
(That's mildly complicated by the fact that you didn't send me parts 6,
8, and 9; I really would rather get the whole series in cases like this.)
Thanks,
jon
next prev parent reply other threads:[~2017-03-31 15:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 20:11 [PATCH 0/9] convert genericirq.tmpl and kernel-api.tmpl to DocBook Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 1/9] scripts/kernel-doc: fix parser for apostrophes Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 2/9] scripts/kernel-doc: fix handling of parameters with parenthesis Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 3/9] genericirq.tmpl: convert it to ReST Mauro Carvalho Chehab
2017-03-31 14:57 ` Jonathan Corbet
2017-03-31 15:45 ` Thomas Gleixner
2017-03-31 18:04 ` Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 4/9] genericirq.rst: add cross-reference links and use monospaced fonts Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 5/9] kernel-api.tmpl: convert it to ReST Mauro Carvalho Chehab
2017-03-31 15:05 ` Jonathan Corbet [this message]
2017-03-31 18:12 ` Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 6/9] kernel-api.rst: fix output of the vsnprintf() documentation Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 7/9] kernel-api.rst: make it handle lib/crc32.c Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 8/9] kernel-api.rst: fix some complex tags at lib/bitmap.c Mauro Carvalho Chehab
2017-03-30 20:11 ` [PATCH 9/9] kernel-api.rst: fix a series of errors when parsing C files Mauro Carvalho Chehab
2017-03-30 21:06 ` Bjorn Helgaas
2017-04-02 20:34 ` [PATCH 0/9] convert genericirq.tmpl and kernel-api.tmpl to DocBook Jonathan Corbet
2017-04-04 12:34 ` Mauro Carvalho Chehab
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=20170331090537.567730e8@lwn.net \
--to=corbet@lwn.net \
--cc=bigeasy@linutronix.de \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=silvio.fricke@gmail.com \
--cc=tiwai@suse.de \
/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