lkml.org 
[lkml]   [2018]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/8] Move most GPIO documentation to driver-api/gpio/ and ReST
On Fri,  9 Mar 2018 00:40:16 +0100
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:

> The aim of this patchset is to move the GPIO subsystem's documentation
> under Documentation/driver-api/gpio/ such that it is picked up by Sphinx
> and compiled into HTML. I moved everything except for sysfs.txt, because
> this file describes the legacy sysfs ABI, and doesn't seem to serve much
> (non-historical) purpose anymore.
>
> There are still some rough edges:
>
> * I think the API documentation (kernel-doc) should be moved out of
> index.rst into more appropriate files.
> * The headings are arguably wrong, because driver.rst, consumer.rst,
> etc. use the "document title" style, even though they are part of the
> GPIO chapter. But the resulting TOC tree is consistent, and I did not
> want to change almost all headings.
> * Some of the files could use more :c:func:`...` references and general
> ReST polish.
>
> But I don't want to make this patchset too large.

[For future reference, if you're going to CC me on most of a patch series,
I'd really rather get the whole thing so I don't have to go looking for
it.]

From a quick look, it seems like a reasonable RST conversion to me. I do
wonder if sysfs.txt should just be removed, since it documents something
we don't want people to use at this point? Historical purposes are well
served by the repository history.

I'd say changing the headings is worthwhile if it produces a better
result. OTOH I'd be wary of adding too much "polish"; we really want to
retain the readability of the plain-text files.

Anyway, I'm happy to take these through the docs tree or see them go via
GPIO; Linus, what's your preference?

Thanks,

jon

\
 
 \ /
  Last update: 2018-03-09 18:41    [W:0.199 / U:7.884 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site