From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux IOMMU <iommu@lists.linux.dev>
Cc: Jonathan Corbet <corbet@lwn.net>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Samiullah Khawaja <skhawaja@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH v2 2/2] iommupt: Describe @bitnr parameter
Date: Fri, 7 Nov 2025 11:09:41 -0800 [thread overview]
Message-ID: <6b20fde4-e416-4d77-a6d0-32fc3319fc6a@infradead.org> (raw)
In-Reply-To: <20251107081300.13033-4-bagasdotme@gmail.com>
grumble...
On 11/7/25 12:13 AM, Bagas Sanjaya wrote:
> Sphinx reports kernel-doc warnings when making htmldocs:
>
> WARNING: ./drivers/iommu/generic_pt/pt_common.h:361 function parameter 'bitnr' not described in 'pt_test_sw_bit_acquire'
> WARNING: ./drivers/iommu/generic_pt/pt_common.h:371 function parameter 'bitnr' not described in 'pt_set_sw_bit_release'
>
> Describe @bitnr to squash them.
>
> Fixes: bcc64b57b48e ("iommupt: Add basic support for SW bits in the page table")
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> drivers/iommu/generic_pt/pt_common.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iommu/generic_pt/pt_common.h b/drivers/iommu/generic_pt/pt_common.h
> index b5628f47e0db40..3b4e371089140a 100644
> --- a/drivers/iommu/generic_pt/pt_common.h
> +++ b/drivers/iommu/generic_pt/pt_common.h
> @@ -354,6 +354,7 @@ static inline unsigned int pt_max_sw_bit(struct pt_common *common);
> /**
> * pt_test_sw_bit_acquire() - Read a software bit in an item
> * @pts: Entry to set
* @pts: Entry to read
> + * @bitnr: Bit to read
> *
> * Software bits are ignored by HW and can be used for any purpose by the
> * software. This does a test bit and acquire operation.
> @@ -364,6 +365,7 @@ static inline bool pt_test_sw_bit_acquire(struct pt_state *pts,
> /**
> * pt_set_sw_bit_release() - Set a software bit in an item
> * @pts: Entry to set
> + * @bitnr: Bit to read
* @bitnr: Bit to set
> *
> * Software bits are ignored by HW and can be used for any purpose by the
> * software. This does a set bit and release operation.
--
~Randy
next prev parent reply other threads:[~2025-11-07 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 8:12 [PATCH v2 0/2] genpt documentation fixes Bagas Sanjaya
2025-11-07 8:13 ` [PATCH v2 1/2] Documentation: genpt: Don't use code block marker before iommu_amdv1.c include listing Bagas Sanjaya
2025-11-07 8:13 ` [PATCH v2 2/2] iommupt: Describe @bitnr parameter Bagas Sanjaya
2025-11-07 19:09 ` Randy Dunlap [this message]
2025-11-07 10:07 ` [PATCH v2 0/2] genpt documentation fixes Joerg Roedel
2025-11-07 19:16 ` Randy Dunlap
2025-11-07 23:15 ` Bagas Sanjaya
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=6b20fde4-e416-4d77-a6d0-32fc3319fc6a@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=corbet@lwn.net \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=robin.murphy@arm.com \
--cc=skhawaja@google.com \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®