From: Jonathan Corbet <corbet@lwn.net>
To: Sebastian Reichel <sre@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] docs: Pull HSI documentation together
Date: Tue, 6 Sep 2016 09:12:21 -0600 [thread overview]
Message-ID: <20160906091221.064e30c9@lwn.net> (raw)
In-Reply-To: <20160823002018.7hvtdjumltmmtvrl@earth>
On Tue, 23 Aug 2016 02:20:19 +0200
Sebastian Reichel <sre@kernel.org> wrote:
> Thanks for doing this. I like the resulting HTML. I'm a bit confused
> by the rendering of the struct sections, though. Initially I thought
> the blue box with "struct xyz" is an empty table (= there are no
> members).
[Getting back to this finally]
The theme needs a fair amount of work still; we've not put much effort
into making it look as good as it should. Maybe that should be my next
project...
> Also I think it would be better to split serial-interfaces.rst into
> the different subsystems. It generates different sections anyways.
You're right, I shouldn't have tried to stick them together like that.
The next attempt, hitting an internet near you shortly, will split them
apart.
Thanks,
jon
next prev parent reply other threads:[~2016-09-06 15:17 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 [this message]
2016-08-23 14:43 ` [PATCH 0/3] RFC: The beginning of a proper driver-api book Mauro Carvalho Chehab
2016-08-26 9:34 ` 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=20160906091221.064e30c9@lwn.net \
--to=corbet@lwn.net \
--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