From: Mikulas Patocka <mpatocka@redhat.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Device Mapper <dm-devel@lists.linux.dev>,
Matthew Sakai <msakai@redhat.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"J. corwin Coburn" <corwin@hurlbutnet.net>
Subject: Re: [PATCH] dm-vdo: Promote dm-vdo title to title heading
Date: Fri, 15 Aug 2025 17:26:03 +0200 (CEST) [thread overview]
Message-ID: <44c7bffa-63c4-5aeb-0b58-f2b16da34331@redhat.com> (raw)
In-Reply-To: <20250815080313.25132-1-bagasdotme@gmail.com>
Applied, thanks.
Mikulas
On Fri, 15 Aug 2025, Bagas Sanjaya wrote:
> dm-vdo docs currently has no explicit title heading but instead there
> are multiple section headings as top-level heading. As such, these
> sections are rendered as titles and inflates number of entries in the
> toctree index.
>
> Promote the first section heading ("dm-vdo") to title heading.
>
> Fixes: 04bf7ac646ab ("dm: add documentation for dm-vdo target")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> Documentation/admin-guide/device-mapper/vdo.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/admin-guide/device-mapper/vdo.rst b/Documentation/admin-guide/device-mapper/vdo.rst
> index a14e6d3e787c91..8a67b320a97b58 100644
> --- a/Documentation/admin-guide/device-mapper/vdo.rst
> +++ b/Documentation/admin-guide/device-mapper/vdo.rst
> @@ -1,5 +1,6 @@
> .. SPDX-License-Identifier: GPL-2.0-only
>
> +======
> dm-vdo
> ======
>
> --
> An old man doll... just what I always wanted! - Clara
>
prev parent reply other threads:[~2025-08-15 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 8:03 Bagas Sanjaya
2025-08-15 15:26 ` Mikulas Patocka [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=44c7bffa-63c4-5aeb-0b58-f2b16da34331@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=corwin@hurlbutnet.net \
--cc=dm-devel@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msakai@redhat.com \
--cc=snitzer@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
all inboxes | Powered by JetHome®