From: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>,
Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/4] scripts/kernel-doc: Adding cross-reference links to html documentation.
Date: Mon, 17 Aug 2015 10:06:08 -0300 [thread overview]
Message-ID: <55D1DC40.40403@collabora.co.uk> (raw)
In-Reply-To: <20150816221058.0496becc@xps.lwn.net>
On 08/17/2015 01:10 AM, Jonathan Corbet wrote:
> On Tue, 28 Jul 2015 16:45:15 -0300
> Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk> wrote:
>
>> Functions, Structs and Parameters definitions on kernel documentation
>> are pure cosmetic, it only highlights the element.
>>
>> To ease the navigation in the documentation we should use <links> inside
>> those tags so readers can easily jump between methods directly.
>>
>> This was discussed in 2014[1] and is implemented by getting a list
>> of <refentries> from the DocBook XML to generate a database. Then it looks
>> for <function>,<structnames> and <paramdef> tags that matches the ones in
>> the database. As it only links existent references, no broken links are
>> added.
>
> So I had some airplane time today and was able to mess with this some. I
> can't make it break anymore, and it clearly improves the resulting
> documentation, so I've applied it to the docs tree for 4.3.
>
> I want to look at the rest of the stuff a bit more and play with it, but
> it's hard to imagine why we wouldn't want that as well. I'm a bit more
> leery just because it adds another dependency to the build, even if it's
> an optional dependency. My thinking at the moment is to apply it shortly
I totally agree about the dependency stuff. I even discussed it with
Daniel Vetter a bit. I started by writing my-very-own-markup-parser to
put alongside kernel-doc to avoid external dependencies, but it gets too
complex too quickly (specially when dealing with tables and multi-line
stuff). It would be a pain to maintain a something like that, and the
world probably doesn't need yet-another-markup-parser, so I decided to
use another tool.
> after the merge window so it can have a long soak in linux-next before a
> 4.4 merge; hope that sounds good.
It does sound good. Thanks!
>
> Thanks for doing this work,
Glad I could help.
Danilo
next prev parent reply other threads:[~2015-08-17 13:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 18:16 [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 1/4] scripts/kernel-doc: Adding cross-reference links to html documentation Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 2/4] scripts/kernel-doc: Replacing highlights hash by an array Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 3/4] scripts/kernel-doc: Adding infrastructure for markdown support Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 4/4] drm/doc: Convert to markdown Danilo Cesar Lemes de Paula
2015-07-23 20:29 ` [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc Jonathan Corbet
2015-08-13 23:09 ` Danilo Cesar Lemes de Paula
2015-08-13 23:20 ` Jonathan Corbet
2015-08-14 17:26 ` Danilo Cesar Lemes de Paula
2015-07-25 10:20 ` Stephan Mueller
2015-07-28 19:12 ` Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 " Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 1/4] scripts/kernel-doc: Adding cross-reference links to html documentation Danilo Cesar Lemes de Paula
2015-08-17 4:10 ` Jonathan Corbet
2015-08-17 13:06 ` Danilo Cesar Lemes de Paula [this message]
2015-07-28 19:45 ` [PATCH v2 2/4] scripts/kernel-doc: Replacing highlights hash by an array Danilo Cesar Lemes de Paula
2015-11-17 10:40 ` Mauro Carvalho Chehab
2015-11-17 14:44 ` Jonathan Corbet
2015-11-17 15:29 ` Mauro Carvalho Chehab
2015-11-17 15:48 ` Danilo Cesar Lemes de Paula
2015-11-18 0:21 ` Jonathan Corbet
2015-11-18 9:14 ` Mauro Carvalho Chehab
2015-07-28 19:45 ` [PATCH v2 3/4] scripts/kernel-doc: Adding infrastructure for markdown support Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 4/4] drm/doc: Convert to markdown Danilo Cesar Lemes de Paula
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=55D1DC40.40403@collabora.co.uk \
--to=danilo.cesar@collabora.co.uk \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=herbert@gondor.apana.org.au \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@infradead.org \
--cc=smueller@chronox.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