From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the cxl tree
Date: Thu, 17 Jul 2025 17:33:54 +1000 [thread overview]
Message-ID: <20250717173354.34375751@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
Hi all,
After merging the cxl tree, today's linux-next build (htmldocs) produced
this warning:
Documentation/core-api/cleanup:7: include/linux/cleanup.h:73: ERROR: Unexpected indentation. [docutils]
Documentation/core-api/cleanup:7: include/linux/cleanup.h:74: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Introduced by commit
857d18f23ab1 ("cleanup: Introduce ACQUIRE() and ACQUIRE_ERR() for conditional locks")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-17 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 7:33 Stephen Rothwell [this message]
2025-07-17 16:30 ` [PATCH] cleanup: Fix documentation build error for ACQUIRE updates Dan Williams
2025-07-17 17:12 ` Dave Jiang
2025-07-18 2:47 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2025-06-10 4:26 linux-next: build warning after merge of the cxl tree Stephen Rothwell
2025-06-10 15:50 ` Dave Jiang
2025-02-26 4:49 Stephen Rothwell
2025-02-26 16:01 ` Dave Jiang
2024-09-12 8:30 Stephen Rothwell
2024-03-14 3:13 Stephen Rothwell
2024-03-15 1:14 ` Dan Williams
2023-10-30 5:05 Stephen Rothwell
2021-05-20 6:03 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=20250717173354.34375751@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.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