From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Gunthorpe <jgg@nvidia•com>
Cc: Jason Gunthorpe <jgg@ziepe•ca>,
Nicolin Chen <nicolinc@nvidia•com>, Yi Liu <yi.l.liu@intel•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the iommufd tree
Date: Fri, 31 Mar 2023 15:31:46 +1100 [thread overview]
Message-ID: <20230331153146.478c4d56@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Hi all,
After merging the iommufd tree, today's linux-next build (htmldocs)
produced this warning:
drivers/iommu/iommufd/device.c:674: warning: Excess function parameter 'ioas_id' description in 'iommufd_access_create'
Introduced by commits
7540af571dc7 ("iommufd: Create access in vfio_iommufd_emulated_bind()")
8003e9a6c169 ("vfio-iommufd: Make vfio_iommufd_emulated_bind() return iommufd_access ID")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-03-31 4:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 4:31 Stephen Rothwell [this message]
2023-03-31 5:09 ` linux-next: build warning after merge of the iommufd tree Nicolin Chen
2023-03-31 17:44 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 8:35 Stephen Rothwell
2025-07-11 14:04 ` Jason Gunthorpe
2025-07-11 8:25 Stephen Rothwell
2025-07-11 13:38 ` Jason Gunthorpe
2025-03-21 8:36 Stephen Rothwell
2025-03-21 11:39 ` Jason Gunthorpe
2025-03-26 2:43 ` Valdis Klētnieks
2025-03-18 10:33 Stephen Rothwell
2025-03-28 6:57 ` Stephen Rothwell
2025-03-28 11:49 ` Bagas Sanjaya
2023-03-31 4:41 Stephen Rothwell
2023-03-31 17:45 ` Jason Gunthorpe
2022-11-08 5:51 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=20230331153146.478c4d56@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jgg@nvidia$(echo .)com \
--cc=jgg@ziepe$(echo .)ca \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nicolinc@nvidia$(echo .)com \
--cc=yi.l.liu@intel$(echo .)com \
/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