Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1336821
| From | Daniel Vetter <daniel.vetter@ffwll.ch> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Kernel docs: muddying the waters a bit |
| Date | 2016-02-17 23:30 +0100 |
| Message-ID | <r3iLE-4sg-11@gated-at.bofh.it> (permalink) |
| References | <r1Qoq-1Y5-17@gated-at.bofh.it> <r1TcC-3Ps-7@gated-at.bofh.it> <r23Yn-2zC-11@gated-at.bofh.it> <r3iBY-4nq-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Feb 17, 2016 at 11:14 PM, Jonathan Corbet <corbet@lwn.net> wrote: > On Sun, 14 Feb 2016 13:27:04 +0100 > Daniel Vetter <daniel.vetter@ffwll.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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Kernel docs: muddying the waters a bit Jonathan Corbet <corbet@lwn.net> - 2016-02-13 23:00 +0100
Re: Kernel docs: muddying the waters a bit Keith Packard <keithp@keithp.com> - 2016-02-14 02:00 +0100
Re: Kernel docs: muddying the waters a bit Daniel Vetter <daniel.vetter@ffwll.ch> - 2016-02-14 13:30 +0100
Re: Kernel docs: muddying the waters a bit Keith Packard <keithp@keithp.com> - 2016-02-14 17:30 +0100
Re: Kernel docs: muddying the waters a bit Jonathan Corbet <corbet@lwn.net> - 2016-02-17 23:20 +0100
Re: Kernel docs: muddying the waters a bit Daniel Vetter <daniel.vetter@ffwll.ch> - 2016-02-17 23:30 +0100
Re: Kernel docs: muddying the waters a bit Jani Nikula <jani.nikula@intel.com> - 2016-02-18 10:20 +0100
Re: Kernel docs: muddying the waters a bit Daniel Vetter <daniel.vetter@ffwll.ch> - 2016-02-18 10:30 +0100
Re: Kernel docs: muddying the waters a bit Mauro Carvalho Chehab <mchehab@osg.samsung.com> - 2016-02-18 11:30 +0100
Re: Kernel docs: muddying the waters a bit Jani Nikula <jani.nikula@intel.com> - 2016-02-18 12:30 +0100
Re: Kernel docs: muddying the waters a bit Hans Verkuil <hverkuil@xs4all.nl> - 2016-02-18 13:10 +0100
Re: Kernel docs: muddying the waters a bit Mauro Carvalho Chehab <mchehab@osg.samsung.com> - 2016-02-18 13:50 +0100
Re: Kernel docs: muddying the waters a bit Patrick Boettcher <patrick.boettcher@posteo.de> - 2016-02-18 14:40 +0100
Re: Kernel docs: muddying the waters a bit Mauro Carvalho Chehab <mchehab@osg.samsung.com> - 2016-02-18 13:10 +0100
Re: Kernel docs: muddying the waters a bit Jonathan Corbet <corbet@lwn.net> - 2016-02-18 14:10 +0100
Re: Kernel docs: muddying the waters a bit Daniel Vetter <daniel.vetter@ffwll.ch> - 2016-02-18 15:50 +0100
Re: Kernel docs: muddying the waters a bit Jani Nikula <jani.nikula@intel.com> - 2016-02-16 09:30 +0100
Re: Kernel docs: muddying the waters a bit Jonathan Corbet <corbet@lwn.net> - 2016-02-16 17:10 +0100
Re: Kernel docs: muddying the waters a bit Jani Nikula <jani.nikula@intel.com> - 2016-02-16 18:20 +0100
Re: Kernel docs: muddying the waters a bit Keith Packard <keithp@keithp.com> - 2016-02-16 20:20 +0100
Re: Kernel docs: muddying the waters a bit Jonathan Corbet <corbet@lwn.net> - 2016-02-16 21:00 +0100
Re: Kernel docs: muddying the waters a bit Keith Packard <keithp@keithp.com> - 2016-02-17 01:10 +0100
csiph-web