From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Steven Royer <seroyer@linux.ibm.com>
Subject: Re: [PATCH] Documentation: add ibmvmc to toctree(index) and fix warnings
Date: Mon, 14 Jan 2019 08:46:15 -0700 [thread overview]
Message-ID: <20190114084615.4f38b265@lwn.net> (raw)
In-Reply-To: <bd222e7e-33cd-37ce-f702-238a8e93dfc8@infradead.org>
On Sun, 13 Jan 2019 19:21:46 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> Fix Sphinx warnings in ibmvmc.rst, add an index.rst file in
> Documentation/misc-devices/, and insert that index file into the
> top-level index file.
>
> Documentation/misc-devices/ibmvmc.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent.
> Documentation/misc-devices/ibmvmc.rst:: WARNING: document isn't included in any toctree
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Steven Royer <seroyer@linux.ibm.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
Rather than make another new top-level entry to add to the mess there, I
do wonder if this isn't better placed in the driver-api manual. I *think*
that's appropriate, though the document is a bit vague to use that way.
Oh well, bringing it in and killing some warnings is better than what we
have now, so I've applied it. We can always move it around later.
Thanks,
jon
prev parent reply other threads:[~2019-01-14 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 3:21 [PATCH] Documentation: add ibmvmc to toctree(index) and fix warnings Randy Dunlap
2019-01-14 15:46 ` 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=20190114084615.4f38b265@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=seroyer@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.