From: Lu Baolu <baolu.lu@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: baolu.lu@linux.intel.com,
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the arm64 tree
Date: Thu, 26 Nov 2020 16:46:31 +0800 [thread overview]
Message-ID: <701c6589-b263-98bf-e48f-1eb890ff5856@linux.intel.com> (raw)
In-Reply-To: <20201126174851.200e0e58@canb.auug.org.au>
Hi Stephen,
On 2020/11/26 14:48, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm64 tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> Documentation/ABI/testing/sysfs-kernel-iommu_groups:38: WARNING: Unexpected indentation.
> Documentation/ABI/testing/sysfs-kernel-iommu_groups:38: WARNING: Block quote ends without a blank line; unexpected unindent.
> Documentation/ABI/testing/sysfs-kernel-iommu_groups:38: WARNING: Enumerated list ends without a blank line; unexpected unindent.
> Documentation/ABI/testing/sysfs-kernel-iommu_groups:38: WARNING: Unexpected indentation.
> Documentation/ABI/testing/sysfs-kernel-iommu_groups:38: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> Caused by commit
>
> 63a816749d86 ("iommu: Document usage of "/sys/kernel/iommu_groups/<grp_id>/type" file")
>
Thanks for letting us know this. I will post a patch to fix it.
Best regards,
baolu
next prev parent reply other threads:[~2020-11-26 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 6:48 linux-next: build warnings after merge of the arm64 tree Stephen Rothwell
2020-11-26 8:46 ` Lu Baolu [this message]
2020-11-26 8:51 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2020-11-10 6:54 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=701c6589-b263-98bf-e48f-1eb890ff5856@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sai.praneeth.prakhya@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=will@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