From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Gunthorpe <jgg@nvidia•com>
Cc: Jason Gunthorpe <jgg@ziepe•ca>,
Joao Martins <joao.m.martins@oracle•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: Mon, 23 Oct 2023 16:47:21 +1100 [thread overview]
Message-ID: <20231023164721.1cb43dd6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
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'
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")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-23 5:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 5:47 Stephen Rothwell [this message]
2023-10-23 10:43 ` linux-next: build warnings after merge of the iommufd tree Joao Martins
-- 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=20231023164721.1cb43dd6@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jgg@nvidia$(echo .)com \
--cc=jgg@ziepe$(echo .)ca \
--cc=joao.m.martins@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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