[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKMK7uEqbSrhc2nh0LjC1fztciM4eTjtKE9T_wMVCqAkkTnzkA@mail.gmail.com>
Date: Wed, 17 Feb 2016 23:29:41 +0100
From: Daniel Vetter <daniel.vetter@...ll.ch>
To: Jonathan Corbet <corbet@....net>
Cc: Keith Packard <keithp@...thp.com>,
LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
Jani Nikula <jani.nikula@...el.com>
Subject: Re: Kernel docs: muddying the waters a bit
On Wed, Feb 17, 2016 at 11:14 PM, Jonathan Corbet <corbet@....net> wrote:
> On Sun, 14 Feb 2016 13:27:04 +0100
> Daniel Vetter <daniel.vetter@...ll.ch> wrote:
>
>> One concern/open I have for pro/cons are the hyperlinks from kerneldoc
>> comments. Currently we have the postproc hack, iirc Jani's patches
>> generated links native when extracting the kerneldoc. What's the
>> solution with spinx?
>
> So I've been trying to figure out what this refers to. Is this the
> cross-reference links within the document? When I did my sphinx hack it
> used a technique that, shall we say, strongly resembles what Jani's
> patches did. One difference is that Sphinx has the concept of
> "functions" built into it, so I use function references for those.
That's what I meant. As long as I can type in stuff like func(),
&struct and similar and get a link for it automatically (plus anywhere
else in the templated stuff for function headers) I'm really happy.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
Powered by blists - more mailing lists