From: Jonathan Corbet <corbet@lwn.net>
To: Graham Whaley <graham.whaley@linux.intel.com>
Cc: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
daniel.vetter@intel.com
Subject: Re: [RFC] Docs: drm: Move KMS properties table out to source files
Date: Mon, 28 Sep 2015 11:33:33 -0600 [thread overview]
Message-ID: <20150928113333.1aca535b@lwn.net> (raw)
In-Reply-To: <1443433019.3639.9.camel@linux.intel.com>
On Mon, 28 Sep 2015 10:36:59 +0100
Graham Whaley <graham.whaley@linux.intel.com> wrote:
> I've still not thought of a way of tweaking the kernel-doc and pandoc
> processing to work around this either, as they are done as different
> passes/phases that neither has knowledge about the others
> requirements.
>
> As it stands, I'm failing to find a method to break out the DRM table
> into markdown tables that I believe works, fundamentally due to this
> 'incompatibility' between the kernel-doc and pandoc_markdown processing
> phases around the highlight processing.
This sort of thing is why I'm increasingly nervous about this one-off mix
of doc-generation tools we're putting together. Sigh.
One possibility might be to have kernel-doc understand some sort of table
notation of its own and make it do the right thing.
Another might be to have kernel-doc format unconditionally to markdown
(or ReST, or something) all the time, then have the secondary processor
handle everything from there. A bigger change, obviously. Probably not
something anybody wants to face, but we may reach a point where we need
to consider having less than three independent formatting tools in the
mix. I *may* get a chance to mess with this idea in the next week or so,
but no promises.
jon
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-09-28 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 13:50 [RFC] Docs: drm: Move KMS properties table out to source files Graham Whaley
2015-09-02 14:14 ` Jani Nikula
2015-09-02 15:28 ` Daniel Vetter
2015-09-02 15:30 ` Daniel Vetter
2015-09-22 10:22 ` Graham Whaley
2015-09-22 19:03 ` Danilo Cesar Lemes de Paula
2015-09-28 9:36 ` Graham Whaley
2015-09-28 12:44 ` Daniel Vetter
2015-09-28 17:33 ` Jonathan Corbet [this message]
2015-11-13 19:19 ` Graham Whaley
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=20150928113333.1aca535b@lwn.net \
--to=corbet@lwn.net \
--cc=daniel.vetter@intel.com \
--cc=danilo.cesar@collabora.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=graham.whaley@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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