From: Jonathan Corbet <corbet@lwn.net>
To: Matthew Wilcox <mawilcox@microsoft.com>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel-doc: Handle returning pointers to pointers
Date: Mon, 23 Jan 2017 08:24:29 -0700 [thread overview]
Message-ID: <20170123082429.2e48b52f@lwn.net> (raw)
In-Reply-To: <BY2PR21MB003639DCA79088A8003AB4FECB720@BY2PR21MB0036.namprd21.prod.outlook.com>
On Mon, 23 Jan 2017 15:14:51 +0000
Matthew Wilcox <mawilcox@microsoft.com> wrote:
> > I maintain my own stack of "linuxdoc" with a python version
> > of the kernel-doc script (hosted on github). It uses the same
> > regexes as the perl version (using a python rewrite here has some
> > other benefits, one you will see below). I merged your patch:
>
> Are there plans to merge that? It feels so odd to have a python script calling a perl script ...
I pushed back pretty hard on it last year; my feeling at the time was that
the Sphinx transition had enough moving parts as it was. I do think we
can reconsider it now, though. It's not as if the perl kerneldoc script
is a thing of great beauty in need of preservation.
Markus, would you consider sending out a new patch set for review? What I
would like to do see is something adding the new script for the Sphinx
toolchain, while leaving the DocBook build unchanged, using the old
script. We could then delete it once the last template file has moved
over.
4.12 would be the probable merge target; it's a big enough change that I'd
like to have it in -next for a full development cycle.
Thanks,
jon
next prev parent reply other threads:[~2017-01-23 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 8:18 Matthew Wilcox
2017-01-23 12:26 ` Markus Heiser
2017-01-23 15:14 ` Matthew Wilcox
2017-01-23 15:24 ` Jonathan Corbet [this message]
2017-01-24 6:58 ` Markus Heiser
2017-01-24 15:35 ` Matthew Wilcox
2017-01-24 20:00 ` Markus Heiser
2017-01-26 22:25 ` Jonathan Corbet
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=20170123082429.2e48b52f@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mawilcox@microsoft.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
all inboxes | Powered by JetHome®