All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Nicolin Chen <nicolinc@nvidia.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, 11 Jul 2025 11:04:10 -0300	[thread overview]
Message-ID: <20250711140410.GB1951027@nvidia.com> (raw)
In-Reply-To: <20250711183526.5c9df5ea@canb.auug.org.au>

On Fri, Jul 11, 2025 at 06:35:26PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the iommufd tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> include/uapi/linux/iommufd.h:607: warning: cannot understand function prototype: 'struct iommu_hw_info_tegra241_cmdqv '
> 
> Introduced by commit
> 
>   b135de24cfc0 ("iommu/tegra241-cmdqv: Add user-space use support")
> 
> You forgot the "struct" in the kerneldoc comment.

I fixed it with this:

--- a/include/uapi/linux/iommufd.h
+++ b/include/uapi/linux/iommufd.h
@@ -592,8 +592,9 @@ struct iommu_hw_info_arm_smmuv3 {
 };
 
 /**
- * iommu_hw_info_tegra241_cmdqv - NVIDIA Tegra241 CMDQV Hardware Information
- *                                (IOMMU_HW_INFO_TYPE_TEGRA241_CMDQV)
+ * struct iommu_hw_info_tegra241_cmdqv - NVIDIA Tegra241 CMDQV Hardware
+ *         Information (IOMMU_HW_INFO_TYPE_TEGRA241_CMDQV)
+ *
  * @flags: Must be 0
  * @version: Version number for the CMDQ-V HW for PARAM bits[03:00]
  * @log2vcmdqs: Log2 of the total number of VCMDQs for PARAM bits[07:04]


Thanks,
Jason



  reply	other threads:[~2025-07-11 14:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  8:35 linux-next: build warning after merge of the iommufd tree Stephen Rothwell
2025-07-11 14:04 ` Jason Gunthorpe [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2023-03-31  4:31 Stephen Rothwell
2023-03-31  5:09 ` Nicolin Chen
2023-03-31 17:44   ` 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=20250711140410.GB1951027@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 \
    /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.