From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the iommufd tree
Date: Thu, 10 Nov 2022 18:29:38 +1100 [thread overview]
Message-ID: <20221110182938.40ce2651@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
Hi all,
After merging the iommufd tree, today's linux-next build (htmldocs)
produced these warnings:
drivers/iommu/iommufd/device.c:1: warning: no structured comments found
drivers/iommu/iommufd/main.c:1: warning: no structured comments found
Introduced by commit
f3873afb9d7e ("iommufd: Document overview of iommufd")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-11-10 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 7:29 Stephen Rothwell [this message]
2022-11-10 18:27 ` linux-next: build warnings after merge of the iommufd tree Jason Gunthorpe
2023-10-23 5:47 Stephen Rothwell
2023-10-23 10:43 ` Joao Martins
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=20221110182938.40ce2651@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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).