From: Jason Gunthorpe <jgg@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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: Re: linux-next: build warnings after merge of the iommufd tree
Date: Thu, 10 Nov 2022 14:27:36 -0400 [thread overview]
Message-ID: <Y21CmMmp191LTK2J@nvidia.com> (raw)
In-Reply-To: <20221110182938.40ce2651@canb.auug.org.au>
On Thu, Nov 10, 2022 at 06:29:38PM +1100, Stephen Rothwell wrote:
> 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
This fix was waiting an ack before I could include it.
All is sorted out now, thanks
Jason
next prev parent reply other threads:[~2022-11-10 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 7:29 linux-next: build warnings after merge of the iommufd tree Stephen Rothwell
2022-11-10 18:27 ` Jason Gunthorpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 5:47 Stephen Rothwell
2023-10-23 10:43 ` Joao Martins
2025-03-18 10:45 Stephen Rothwell
2025-03-18 16:32 ` Nicolin Chen
2025-11-26 1:59 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=Y21CmMmp191LTK2J@nvidia.com \
--to=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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