public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joerg Roedel <joro@8bytes•org>
Cc: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd•com>,
	Will Deacon <will@kernel•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 iommu tree
Date: Wed, 16 Jul 2025 20:42:07 +1000	[thread overview]
Message-ID: <20250716204207.73869849@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

Hi all,

After merging the iommu tree, today's linux-next build (htmldocs)
produced this warning:

Documentation/ABI/testing/debugfs-amd-iommu:31: ERROR: Unexpected indentation. [docutils]
Documentation/ABI/testing/debugfs-amd-iommu:31: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/ABI/testing/debugfs-amd-iommu:31: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]

Introduced by commit

  39215bb3b0d9 ("iommu/amd: Add documentation for AMD IOMMU debugfs support")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-07-16 10:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 10:42 Stephen Rothwell [this message]
2025-07-17 10:04 ` linux-next: build warning after merge of the iommu tree Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2025-11-06  3:39 Stephen Rothwell
2024-07-09  9:06 Stephen Rothwell
2024-07-09 10:08 ` Will Deacon
2021-06-08  3:56 Stephen Rothwell
2019-02-27  2:20 Stephen Rothwell
2019-02-27 18:48 ` sathyanarayanan kuppuswamy
2018-11-08  1:39 Stephen Rothwell
2018-11-08  9:30 ` Joerg Roedel

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=20250716204207.73869849@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dheerajkumar.srivastava@amd$(echo .)com \
    --cc=joro@8bytes$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=will@kernel$(echo .)org \
    /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