From: Joao Martins <joao.m.martins@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
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: Mon, 23 Oct 2023 11:43:10 +0100 [thread overview]
Message-ID: <15de3f3c-17f6-4fe3-8e22-8e7e7361ed3e@oracle.com> (raw)
In-Reply-To: <20231023164721.1cb43dd6@canb.auug.org.au>
On 23/10/2023 06:47, Stephen Rothwell wrote:
> Hi all,
>
> After merging the iommufd tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> include/uapi/linux/iommufd.h:433: warning: expecting prototype for enum iommufd_hw_info_capabilities. Prototype was for enum iommufd_hw_capabilities instead
> include/uapi/linux/iommufd.h:497: warning: Function parameter or member '__reserved' not described in 'iommu_hwpt_set_dirty_tracking'
> include/uapi/linux/iommufd.h:512: warning: expecting prototype for enum iommufd_get_dirty_bitmap_flags. Prototype was for enum iommufd_hwpt_get_dirty_bitmap_flags instead
> include/uapi/linux/iommufd.h:542: warning: Function parameter or member '__reserved' not described in 'iommu_hwpt_get_dirty_bitmap'
>
Thanks
I've fixed these warnings in the offending patches below; for the next version.
> Introduced by commits
>
> f87900f25050 ("iommufd: Add a flag to skip clearing of IOPTE dirty")
> d2b3a545cdcc ("iommufd: Add capabilities to IOMMU_GET_HW_INFO")
> 1337d793ea25 ("iommufd: Add IOMMU_HWPT_GET_DIRTY_BITMAP")
> ccccda6d18bd ("iommufd: Add IOMMU_HWPT_SET_DIRTY_TRACKING")
>
next prev parent reply other threads:[~2023-10-23 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 5:47 Stephen Rothwell
2023-10-23 10:43 ` Joao Martins [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-26 1:59 Stephen Rothwell
2025-03-18 10:45 Stephen Rothwell
2025-03-18 16:32 ` Nicolin Chen
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=15de3f3c-17f6-4fe3-8e22-8e7e7361ed3e@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--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
all inboxes | Powered by JetHome®