From: Jonathan Corbet <corbet@lwn.net>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] mux: add overview and add to driver-api docs
Date: Mon, 11 Dec 2017 14:52:39 -0700 [thread overview]
Message-ID: <20171211145239.25455568@lwn.net> (raw)
In-Reply-To: <20171211082943.5796-1-peda@axentia.se>
On Mon, 11 Dec 2017 09:29:41 +0100
Peter Rosin <peda@axentia.se> wrote:
> Don't know if this is worth adding, but it might answer at least a few
> questions.
>
> It looks ok when I view the htmldocs output, but I'm not all that certain
> this is good to go?
Almost, but I have one request: the new mux.rst file is rather
unenlightening for somebody who reads it directly in the docs tree. If
you want to keep the bulk of the text in the source I can live with that,
but can mux.rst at least get an introductory paragraph saying what it
covers (what *is* the mux subsystem?) and why readers might want to go
find the rest?
Thanks,
jon
prev parent reply other threads:[~2017-12-11 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 8:29 Peter Rosin
2017-12-11 8:29 ` [PATCH 1/2] mux: core: add a brief overview of the subsystem Peter Rosin
2017-12-11 8:29 ` [PATCH 2/2] docs: add mux docs to the driver-api docs Peter Rosin
2017-12-11 21:52 ` Jonathan Corbet [this message]
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=20171211145239.25455568@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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
all inboxes | Powered by JetHome®