From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alasdair G Kergon <agk@redhat.com>, Mike Snitzer <snitzer@redhat.com>
Cc: Tushar Sugandhi <tusharsu@linux.microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the device-mapper tree
Date: Tue, 10 Aug 2021 19:31:49 +1000 [thread overview]
Message-ID: <20210810193149.4ad4714a@canb.auug.org.au> (raw)
In-Reply-To: <20210721173432.3dce9ce3@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Hi all,
On Wed, 21 Jul 2021 17:34:32 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the device-mapper tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/admin-guide/device-mapper/dm-ima.rst:29: WARNING: Unexpected indentation.
> Documentation/admin-guide/device-mapper/dm-ima.rst:52: WARNING: Definition list ends without a blank line; unexpected unindent.
> Documentation/admin-guide/device-mapper/dm-ima.rst:109: WARNING: Unexpected indentation.
> Documentation/admin-guide/device-mapper/dm-ima.rst:129: WARNING: Unexpected indentation.
>
> Introduced by commit
>
> e820ba87f9d1 ("dm: add documentation for IMA measurement support")
I am still getting these warnings.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-10 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 7:34 linux-next: build warning after merge of the device-mapper tree Stephen Rothwell
2021-08-10 9:31 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 3:42 Stephen Rothwell
2021-01-22 6:56 Stephen Rothwell
2020-07-09 3:26 Stephen Rothwell
2020-07-09 4:38 ` yangerkun
2019-02-20 2:15 Stephen Rothwell
2019-02-20 3:35 ` Mike Snitzer
2018-09-18 1:53 Stephen Rothwell
2017-12-11 2:05 Stephen Rothwell
2017-12-11 5:24 ` Mike Snitzer
2017-12-11 5:43 ` Stephen Rothwell
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=20210810193149.4ad4714a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=tusharsu@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).