From: Mikulas Patocka <mpatocka@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
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, 30 Jul 2024 13:54:13 +0200 (CEST) [thread overview]
Message-ID: <aa4b337-e1dd-4091-ab2-6b41de205fd1@redhat.com> (raw)
In-Reply-To: <20240730200737.67bb4d4f@canb.auug.org.au>
On Tue, 30 Jul 2024, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 10 Jul 2024 17:48:39 +0200 (CEST) Mikulas Patocka <mpatocka@redhat.com> wrote:
> >
> > On Wed, 10 Jul 2024, Stephen Rothwell wrote:
> >
> > > On Tue, 9 Jul 2024 11:56:27 +0200 (CEST) Mikulas Patocka <mpatocka@redhat.com> wrote:
> > > >
> > > > On Tue, 9 Jul 2024, Stephen Rothwell wrote:
> > > >
> > > > > After merging the device-mapper tree, today's linux-next build (htmldocs)
> > > > > produced this warning:
> > > > >
> > > > > Documentation/admin-guide/device-mapper/dm-crypt.rst:168: ERROR: Unexpected indentation.
> > > > >
> > > > > Introduced by commit
> > > > >
> > > > > 04a1020ad350 ("dm-crypt: limit the size of encryption requests")
> > > >
> > > > How should it be fixed? Delete the '-' character? Or some other change?
> > >
> > > Looking a few lines above shows indented paragraphs without the '-'
> > > which seems to work.
> >
> > I hopefully fixed that.
>
> I am sill seeing this warning.
Hi
So, send a patch for it.
I don't know whats wrong with that documentation file.
Mikulas
next prev parent reply other threads:[~2024-07-30 11:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 8:57 linux-next: build warning after merge of the device-mapper tree Stephen Rothwell
2024-07-09 9:56 ` Mikulas Patocka
2024-07-09 22:28 ` Stephen Rothwell
2024-07-10 15:48 ` Mikulas Patocka
2024-07-30 10:07 ` Stephen Rothwell
2024-07-30 11:54 ` Mikulas Patocka [this message]
2024-07-30 13:36 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 3:42 Stephen Rothwell
2021-07-21 7:34 Stephen Rothwell
2021-08-10 9:31 ` 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=aa4b337-e1dd-4091-ab2-6b41de205fd1@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).