All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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: Re: linux-next: build warning after merge of the iommufd tree
Date: Fri, 31 Mar 2023 14:44:35 -0300	[thread overview]
Message-ID: <ZCccAzdcYLio0Xoa@nvidia.com> (raw)
In-Reply-To: <ZCZrEtNH5YjGjRqS@Asurada-Nvidia>

On Thu, Mar 30, 2023 at 10:09:38PM -0700, Nicolin Chen wrote:
> Thanks for reporting.
> 
> On Fri, Mar 31, 2023 at 03:31:46PM +1100, Stephen Rothwell wrote:
> > 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()")
> 
> Should have dropped that line from kdoc in this commit.
> 
> diff --git a/drivers/iommu/iommufd/device.c b/drivers/iommu/iommufd/device.c
> index fca09bb4e839..d791ab5830b4 100644
> --- a/drivers/iommu/iommufd/device.c
> +++ b/drivers/iommu/iommufd/device.c
> @@ -795,7 +795,6 @@ void iommufd_access_destroy_object(struct iommufd_object *obj)
>  /**
>   * iommufd_access_create - Create an iommufd_access
>   * @ictx: iommufd file descriptor
> - * @ioas_id: ID for a IOMMUFD_OBJ_IOAS
>   * @ops: Driver's ops to associate with the access
>   * @data: Opaque data to pass into ops functions
>   *

Got it thanks

Jason

  reply	other threads:[~2023-03-31 17:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  4:31 linux-next: build warning after merge of the iommufd tree Stephen Rothwell
2023-03-31  5:09 ` Nicolin Chen
2023-03-31 17:44   ` Jason Gunthorpe [this message]
  -- 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=ZCccAzdcYLio0Xoa@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=sfr@canb.auug.org.au \
    --cc=yi.l.liu@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.