From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jani Nikula <jani.nikula@intel.com>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH 0/3] RFC: The beginning of a proper driver-api book
Date: Tue, 23 Aug 2016 11:43:07 -0300 [thread overview]
Message-ID: <20160823114307.1bf0a3c9@vento.lan> (raw)
In-Reply-To: <1471899463-5774-1-git-send-email-corbet@lwn.net>
Em Mon, 22 Aug 2016 14:57:40 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> This short series convers device-drivers.tmpl into the RST format, splits
> it up, and sets up the result under Documentation/driver-api/. For added
> fun, I've taken one top-level file (hsi.txt) and folded it into the
> document as a way of showing the direction I'm thinking I would like things
> to go. There is plenty more of this sort of work that could be done, to
> say the least - this is just a beginning!
>
> The formatted results can be seen at:
>
> http://static.lwn.net/kerneldoc/driver-api/index.html
Thanks for doing that! IMHO, the conversion of this book is indeed
one of the first things to be done.
> As part of the long-term task to turn Documentation/ into less of a horror
> movie, I'd like to collect documentation of the driver-specific API here.
> Arguably gpu/ and the media API stuff should eventually move here, though
> we can discuss the color of that particular shed some other day.
Yeah, let's finish converting everything to rst, and then see what would
be the best way to organize it.
I have a split feelings with regards to media kAPI and driver-specific
stuff if it is better to keep it at the device-drivers book, or at a
single media book (with currently has 1031 pages on PDF output),
but let's postpone such discussion.
I'm afraid that we'll end needing to split it more than what would be
desired, in order to fix some issues with the PDF output
part/chapter/section numbering. Unfortunately, ReST markup is too poor
to describe multi-part books, and doesn't have anything to describe
multi-book projects.
> Meanwhile, I'd appreciate comments on the general idea.
I like the general idea of breaking device-drivers.tmpl into multiple
files. IMHO, that will make easier to maintain it long term.
After looking on all 3 patches, they all look good, as a concept.
Yet, IMHO, there are a few things to be fixed before merging it. See
my comments to patch 2/3.
Regards,
Mauro
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> Cc: Sebastian Reichel <sre@kernel.org>
>
> Jonathan Corbet (3):
> Docs: sphinxify device-drivers.tmpl
> docs: split up the driver book
> docs: Pull HSI documentation together
>
> Documentation/DocBook/Makefile | 2 +-
> Documentation/DocBook/device-drivers.tmpl | 521 -------------------------
> Documentation/driver-api/basics.rst | 120 ++++++
> Documentation/driver-api/frame-buffer.rst | 62 +++
> Documentation/driver-api/index.rst | 24 ++
> Documentation/driver-api/infrastructure.rst | 169 ++++++++
> Documentation/driver-api/input.rst | 51 +++
> Documentation/driver-api/message-based.rst | 30 ++
> Documentation/driver-api/miscellaneous.rst | 50 +++
> Documentation/driver-api/serial-interfaces.rst | 189 +++++++++
> Documentation/driver-api/sound.rst | 54 +++
> Documentation/hsi.txt | 75 ----
> Documentation/index.rst | 1 +
> MAINTAINERS | 2 +-
> 14 files changed, 752 insertions(+), 598 deletions(-)
> delete mode 100644 Documentation/DocBook/device-drivers.tmpl
> create mode 100644 Documentation/driver-api/basics.rst
> create mode 100644 Documentation/driver-api/frame-buffer.rst
> create mode 100644 Documentation/driver-api/index.rst
> create mode 100644 Documentation/driver-api/infrastructure.rst
> create mode 100644 Documentation/driver-api/input.rst
> create mode 100644 Documentation/driver-api/message-based.rst
> create mode 100644 Documentation/driver-api/miscellaneous.rst
> create mode 100644 Documentation/driver-api/serial-interfaces.rst
> create mode 100644 Documentation/driver-api/sound.rst
> delete mode 100644 Documentation/hsi.txt
>
Thanks,
Mauro
next prev parent reply other threads:[~2016-08-23 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 20:57 [PATCH 0/3] RFC: The beginning of a proper driver-api book Jonathan Corbet
2016-08-22 20:57 ` [PATCH 1/3] Docs: sphinxify device-drivers.tmpl Jonathan Corbet
2016-08-22 20:57 ` [PATCH 2/3] docs: split up the driver book Jonathan Corbet
2016-08-23 14:30 ` Mauro Carvalho Chehab
2016-08-24 22:46 ` Jonathan Corbet
2016-08-25 1:55 ` Mauro Carvalho Chehab
2016-08-25 20:09 ` Jonathan Corbet
2016-08-22 20:57 ` [PATCH 3/3] docs: Pull HSI documentation together Jonathan Corbet
2016-08-23 0:20 ` Sebastian Reichel
2016-09-06 15:12 ` Jonathan Corbet
2016-08-23 14:43 ` Mauro Carvalho Chehab [this message]
2016-08-26 9:34 ` [PATCH 0/3] RFC: The beginning of a proper driver-api book Markus Heiser
2016-08-26 9:59 ` Mauro Carvalho Chehab
2016-08-26 10:19 ` Jani Nikula
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=20160823114307.1bf0a3c9@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sre@kernel.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