From: Mike Snitzer <snitzer@redhat.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Nikos Tsironis <ntsironis@arrikto.com>,
Ilias Tsitsimpis <iliastsi@arrikto.com>,
Jonathan Corbet <corbet@lwn.net>,
Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: docs: device-mapper: Add dm-clone to documentation index
Date: Tue, 26 Nov 2019 15:16:13 -0500 [thread overview]
Message-ID: <20191126201613.GA3750@redhat.com> (raw)
In-Reply-To: <20191126185627.970-1-geert+renesas@glider.be>
On Tue, Nov 26 2019 at 1:56pm -0500,
Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> When the dm-clone documentation was added, it was not added to the
> documentation index, leading to a warning when building the
> documentation:
>
> Documentation/admin-guide/device-mapper/dm-clone.rst: WARNING: document isn't included in any toctree
>
> Fixes: 7431b7835f554f86 ("dm: add clone target")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/admin-guide/device-mapper/index.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/admin-guide/device-mapper/index.rst b/Documentation/admin-guide/device-mapper/index.rst
> index 4872fb6d29524593..ec62fcc8eeceed83 100644
> --- a/Documentation/admin-guide/device-mapper/index.rst
> +++ b/Documentation/admin-guide/device-mapper/index.rst
> @@ -8,6 +8,7 @@ Device Mapper
> cache-policies
> cache
> delay
> + dm-clone
> dm-crypt
> dm-dust
> dm-flakey
>
I already staged this for 5.5 here:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.5&id=484e0d2b11e1fdd0d17702b282eb2ed56148385f
But I don't plan to send to Linus for a week or 2...
If Jon and/or someone else would like to send it along before then
that'd be fine with me.
next prev parent reply other threads:[~2019-11-26 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 18:56 [PATCH] docs: device-mapper: Add dm-clone to documentation index Geert Uytterhoeven
2019-11-26 20:16 ` Mike Snitzer [this message]
2019-11-26 21:37 ` Jonathan Corbet
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=20191126201613.GA3750@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=corbet@lwn.net \
--cc=dm-devel@redhat.com \
--cc=geert+renesas@glider.be \
--cc=iliastsi@arrikto.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntsironis@arrikto.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox