All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: <oe-kbuild-all@lists.linux.dev>,
	kernel test robot <lkp@intel.com>, Yi Liu <yi.l.liu@intel.com>
Subject: Re: [jgg-iommufd:for-next 36/39] drivers/iommu/iommufd/hw_pagetable.c:101: warning: Function parameter or member 'user_data' not described in 'iommufd_hwpt_paging_alloc'
Date: Tue, 24 Oct 2023 13:27:29 -0700	[thread overview]
Message-ID: <ZTgosVlGp/H/k6pd@Asurada-Nvidia> (raw)
In-Reply-To: <202310250418.NmeDHFgw-lkp@intel.com>

Hi Jason,

On Wed, Oct 25, 2023 at 04:21:08AM +0800, kernel test robot wrote:

> >> drivers/iommu/iommufd/hw_pagetable.c:101: warning: Function parameter or member 'user_data' not described in 'iommufd_hwpt_paging_alloc'
> 
> 
> vim +101 drivers/iommu/iommufd/hw_pagetable.c
> 
> 17bad52708b457 Jason Gunthorpe 2023-07-17   79
> ea4acfac57b9de Jason Gunthorpe 2022-11-29   80  /**
> 3bc7f01ff2de6b Nicolin Chen    2023-10-24   81   * iommufd_hwpt_paging_alloc() - Get a PAGING iommu_domain for a device
> ea4acfac57b9de Jason Gunthorpe 2022-11-29   82   * @ictx: iommufd context
> ea4acfac57b9de Jason Gunthorpe 2022-11-29   83   * @ioas: IOAS to associate the domain with
> 339fbf3ae14426 Jason Gunthorpe 2023-03-01   84   * @idev: Device to get an iommu_domain for
> 89d63875d80ea1 Yi Liu          2023-09-28   85   * @flags: Flags from userspace
> 339fbf3ae14426 Jason Gunthorpe 2023-03-01   86   * @immediate_attach: True if idev should be attached to the hwpt
> ea4acfac57b9de Jason Gunthorpe 2022-11-29   87   *
> 339fbf3ae14426 Jason Gunthorpe 2023-03-01   88   * Allocate a new iommu_domain and return it as a hw_pagetable. The HWPT
> 339fbf3ae14426 Jason Gunthorpe 2023-03-01   89   * will be linked to the given ioas and upon return the underlying iommu_domain
> 339fbf3ae14426 Jason Gunthorpe 2023-03-01   90   * is fully popoulated.
> 70eadc7fc7ef29 Jason Gunthorpe 2023-07-17   91   *
> 70eadc7fc7ef29 Jason Gunthorpe 2023-07-17   92   * The caller must hold the ioas->mutex until after
> 70eadc7fc7ef29 Jason Gunthorpe 2023-07-17   93   * iommufd_object_abort_and_destroy() or iommufd_object_finalize() is called on
> 70eadc7fc7ef29 Jason Gunthorpe 2023-07-17   94   * the returned hwpt.
> ea4acfac57b9de Jason Gunthorpe 2022-11-29   95   */
> 3bc7f01ff2de6b Nicolin Chen    2023-10-24   96  struct iommufd_hwpt_paging *
> 3bc7f01ff2de6b Nicolin Chen    2023-10-24   97  iommufd_hwpt_paging_alloc(struct iommufd_ctx *ictx, struct iommufd_ioas *ioas,
> 89d63875d80ea1 Yi Liu          2023-09-28   98                            struct iommufd_device *idev, u32 flags,
> a6f4f0247d4e7b Nicolin Chen    2023-10-24   99                            bool immediate_attach,
> a6f4f0247d4e7b Nicolin Chen    2023-10-24  100                            const struct iommu_user_data *user_data)

I think we forgot to add this:

----------------------------------
diff --git a/drivers/iommu/iommufd/hw_pagetable.c b/drivers/iommu/iommufd/hw_pagetable.c
index 6e11693617a0..358708973cd7 100644
--- a/drivers/iommu/iommufd/hw_pagetable.c
+++ b/drivers/iommu/iommufd/hw_pagetable.c
@@ -84,6 +84,7 @@ iommufd_hwpt_paging_enforce_cc(struct iommufd_hwpt_paging *hwpt_paging)
  * @idev: Device to get an iommu_domain for
  * @flags: Flags from userspace
  * @immediate_attach: True if idev should be attached to the hwpt
+ * @user_data: Optional user_data pointer
  *
  * Allocate a new iommu_domain and return it as a hw_pagetable. The HWPT
  * will be linked to the given ioas and upon return the underlying iommu_domain
----------------------------------

Thanks
Nic

  reply	other threads:[~2023-10-24 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 20:21 [jgg-iommufd:for-next 36/39] drivers/iommu/iommufd/hw_pagetable.c:101: warning: Function parameter or member 'user_data' not described in 'iommufd_hwpt_paging_alloc' kernel test robot
2023-10-24 20:27 ` Nicolin Chen [this message]
2023-10-24 23:09   ` 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=ZTgosVlGp/H/k6pd@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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.