From: Nicolin Chen <nicolinc@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jason Gunthorpe <jgg@nvidia.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: Tue, 18 Mar 2025 09:32:45 -0700 [thread overview]
Message-ID: <Z9mgLQlIDT596t70@Asurada-Nvidia> (raw)
In-Reply-To: <20250318214534.5476f9ed@canb.auug.org.au>
On Tue, Mar 18, 2025 at 09:45:34PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the iommufd tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> include/uapi/linux/iommufd.h:1024: warning: Enum value 'IOMMU_VEVENTQ_FLAG_LOST_EVENTS' not described in enum 'iommu_veventq_flag'
> include/uapi/linux/iommufd.h:1024: warning: Excess enum value 'IOMMU_VEVENTQ_FLAG_OVERFLOW' description in 'iommu_veventq_flag'
> include/uapi/linux/iommufd.h:1120: warning: Function parameter or struct member 'viommu_id' not described in 'iommu_veventq_alloc'
> include/uapi/linux/iommufd.h:1120: warning: Excess struct member 'viommu' description in 'iommu_veventq_alloc'
>
> Introduced by commit
>
> 50c842dd6cd3 ("iommufd: Add IOMMUFD_OBJ_VEVENTQ and IOMMUFD_CMD_VEVENTQ_ALLOC")
Sent a fix:
https://lore.kernel.org/linux-iommu/20250318163022.709490-1-nicolinc@nvidia.com/
Thanks!
Nicolin
next prev parent reply other threads:[~2025-03-18 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:45 linux-next: build warnings after merge of the iommufd tree Stephen Rothwell
2025-03-18 16:32 ` Nicolin Chen [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-26 1:59 Stephen Rothwell
2023-10-23 5:47 Stephen Rothwell
2023-10-23 10:43 ` Joao Martins
2022-11-10 7:29 Stephen Rothwell
2022-11-10 18:27 ` Jason Gunthorpe
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=Z9mgLQlIDT596t70@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=jgg@nvidia.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