mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muhammad Muzammil <m.muzzammilashraf@gmail.com>
To: jgg@ziepe.ca, kevin.tian@intel.com
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	Muhammad Muzammil <m.muzzammilashraf@gmail.com>
Subject: [PATCH] include: uapi: linux: iommufd.h: fixed kernel-doc warnings
Date: Mon, 23 Oct 2023 15:38:52 +0500	[thread overview]
Message-ID: <20231023103852.28743-1-m.muzzammilashraf@gmail.com> (raw)

Fixed multiple kernel-docs warnings

Signed-off-by: Muhammad Muzammil <m.muzzammilashraf@gmail.com>
---
 include/uapi/linux/iommufd.h | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/include/uapi/linux/iommufd.h b/include/uapi/linux/iommufd.h
index 50f98f01fe10..2211f1b53d6e 100644
--- a/include/uapi/linux/iommufd.h
+++ b/include/uapi/linux/iommufd.h
@@ -419,7 +419,7 @@ enum iommu_hw_info_type {
 };
 
 /**
- * enum iommufd_hw_info_capabilities
+ * enum iommufd_hw_capabilities
  * @IOMMU_HW_CAP_DIRTY_TRACKING: IOMMU hardware support for dirty tracking
  *                               If available, it means the following APIs
  *                               are supported:
@@ -486,6 +486,7 @@ enum iommufd_hwpt_set_dirty_tracking_flags {
  * @size: sizeof(struct iommu_hwpt_set_dirty_tracking)
  * @flags: Combination of enum iommufd_hwpt_set_dirty_tracking_flags
  * @hwpt_id: HW pagetable ID that represents the IOMMU domain
+ * @__reserved: Must be 0
  *
  * Toggle dirty tracking on an HW pagetable.
  */
@@ -499,12 +500,12 @@ struct iommu_hwpt_set_dirty_tracking {
 					  IOMMUFD_CMD_HWPT_SET_DIRTY_TRACKING)
 
 /**
- * enum iommufd_get_dirty_bitmap_flags - Flags for getting dirty bits
- * @IOMMU_GET_DIRTY_BITMAP_NO_CLEAR: Just read the PTEs without clearing any
- *                                   dirty bits metadata. This flag can be
- *                                   passed in the expectation where the next
- *                                   operation is an unmap of the same IOVA
- *                                   range.
+ * enum iommufd_hwpt_get_dirty_bitmap_flags - Flags for getting dirty bits
+ * @IOMMU_HWPT_GET_DIRTY_BITMAP_NO_CLEAR: Just read the PTEs without clearing any
+ *                                        dirty bits metadata. This flag can be
+ *                                        passed in the expectation where the next
+ *                                        operation is an unmap of the same IOVA
+ *                                        range.
  *
  */
 enum iommufd_hwpt_get_dirty_bitmap_flags {
@@ -521,6 +522,7 @@ enum iommufd_hwpt_get_dirty_bitmap_flags {
  * @page_size: page size granularity of each bit in the bitmap
  * @data: bitmap where to set the dirty bits. The bitmap bits each
  *        represent a page_size which you deviate from an arbitrary iova.
+ * @__reserved: Must be 0
  *
  * Checking a given IOVA is dirty:
  *
-- 
2.27.0


             reply	other threads:[~2023-10-23 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 10:38 Muhammad Muzammil [this message]
2023-10-24  9:48 ` Muhammad Muzammil
2023-10-24 11:30   ` Joao Martins

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=20231023103852.28743-1-m.muzzammilashraf@gmail.com \
    --to=m.muzzammilashraf@gmail.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.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®