From: Jani Nikula <jani.nikula@intel.com>
To: Jonathan Corbet <corbet@lwn.net>,
Markus Heiser <markus.heiser@darmarit.de>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Matthew Wilcox <mawilcox@microsoft.com>,
"linux-doc \@ vger . kernel . org List"
<linux-doc@vger.kernel.org>,
"linux-kernel \@ vger . kernel . org List"
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v1 2/6] kernel-doc: replace kernel-doc perl parser with a pure python one (WIP)
Date: Thu, 26 Jan 2017 21:26:16 +0200 [thread overview]
Message-ID: <87a8ad39nr.fsf@intel.com> (raw)
In-Reply-To: <20170126115005.7bf0e4a6@lwn.net>
On Thu, 26 Jan 2017, Jonathan Corbet <corbet@lwn.net> wrote:
> Give me a new kerneldoc that passes those tests, and I'll happily
> merge it. (I have some sympathy with the idea that we should look
> into other parsers, but I would not hold up a new kerneldoc that
> passed those tests on this basis alone.)
I'll just note in passing that having another parser that actually works
for our needs might be a pink unicorn pony. It might exist, it might
not, and someone would have to put in the hours to try to find it, tame
it, and bring it to the kernel. But it would be awesome to
have. Switching to a homebrew Python parser first does not preclude a
unicorn hunt later.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-01-26 19:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 19:52 [RFC PATCH v1 0/6] pure python kernel-doc parser and more Markus Heiser
2017-01-24 19:52 ` [RFC PATCH v1 1/6] kernel-doc: pure python kernel-doc parser (preparation) Markus Heiser
2017-01-24 19:52 ` [RFC PATCH v1 2/6] kernel-doc: replace kernel-doc perl parser with a pure python one (WIP) Markus Heiser
2017-01-25 0:13 ` Jonathan Corbet
2017-01-25 6:37 ` Daniel Vetter
2017-01-25 7:37 ` Markus Heiser
2017-01-25 10:24 ` Jani Nikula
2017-01-25 10:35 ` Daniel Vetter
2017-01-25 19:07 ` Markus Heiser
2017-01-25 20:59 ` Jani Nikula
2017-01-26 9:54 ` Markus Heiser
2017-01-26 10:16 ` Jani Nikula
2017-01-26 18:50 ` Jonathan Corbet
2017-01-26 19:26 ` Jani Nikula [this message]
2017-01-27 9:46 ` Markus Heiser
2017-01-24 19:52 ` [RFC PATCH v1 3/6] kernel-doc: add kerneldoc-lint command Markus Heiser
2017-01-25 6:38 ` Daniel Vetter
2017-01-25 8:21 ` Jani Nikula
2017-01-25 9:34 ` Markus Heiser
2017-01-25 10:08 ` Jani Nikula
2017-01-24 19:52 ` [RFC PATCH v1 4/6] kernel-doc: insert TODOs on kernel-doc errors Markus Heiser
2017-01-24 19:52 ` [RFC PATCH v1 5/6] kernel-doc: add kerneldoc-src2rst command Markus Heiser
2017-01-24 19:52 ` [RFC PATCH v1 6/6] kernel-doc: add man page builder (target mandocs) Markus Heiser
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=87a8ad39nr.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mawilcox@microsoft.com \
--cc=mchehab@infradead.org \
/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