From: Bagas Sanjaya <bagasdotme@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Herbert Xu <herbert@gondor•apana.org.au>
Cc: Meenakshi Aggarwal <meenakshi.aggarwal@nxp•com>,
Pankaj Gupta <pankaj.gupta@nxp•com>,
Linux Crypto List <linux-crypto@vger•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 crypto tree
Date: Mon, 20 Oct 2025 10:34:01 +0700 [thread overview]
Message-ID: <aPWtqT17TiqKTibG@archie.me> (raw)
In-Reply-To: <20251020135339.5df5ec50@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On Mon, Oct 20, 2025 at 01:53:39PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the crypto tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/security/keys/trusted-encrypted.rst:18: ERROR: Unexpected indentation. [docutils]
> Documentation/security/keys/trusted-encrypted.rst:19: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
>
> Introduced by commit
>
> 95c46f40aac4 ("docs: trusted-encrypted: trusted-keys as protected keys")
Fixed by [1].
Thanks.
[1]: https://lore.kernel.org/linux-doc/20251017181135.354411-1-krishnagopi487@gmail.com/
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-20 3:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 2:53 linux-next: build warning after merge of the crypto tree Stephen Rothwell
2025-10-20 3:34 ` Bagas Sanjaya [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 3:07 Stephen Rothwell
2025-06-16 5:31 Stephen Rothwell
2024-10-08 6:29 Stephen Rothwell
2024-02-12 3:48 Stephen Rothwell
2024-02-12 12:59 ` Cabiddu, Giovanni
2022-11-21 1:52 Stephen Rothwell
2022-07-11 10:49 Stephen Rothwell
2019-08-23 3:14 Stephen Rothwell
2019-08-25 18:01 ` Hans de Goede
2019-02-04 0:01 Stephen Rothwell
2018-10-05 5:31 Stephen Rothwell
2018-03-19 1:04 Stephen Rothwell
2018-03-19 5:44 ` Harsh Jain
2018-01-19 1:49 Stephen Rothwell
2018-01-19 4:21 ` Harsh Jain
2018-01-19 5:12 ` Herbert Xu
2017-07-31 2:17 Stephen Rothwell
2017-07-31 13:50 ` Gary R Hook
2016-08-25 1:38 Stephen Rothwell
2016-08-25 6:20 ` Martin Schwidefsky
2016-08-25 7:47 ` Herbert Xu
2016-08-25 11:14 ` 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=aPWtqT17TiqKTibG@archie.me \
--to=bagasdotme@gmail$(echo .)com \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=meenakshi.aggarwal@nxp$(echo .)com \
--cc=pankaj.gupta@nxp$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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