From: Jason Gunthorpe <jgg@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
Nicolin Chen <nicolinc@nvidia.com>,
linux-doc@vger.kernel.org
Subject: Re: [jgunthorpe:iommufd 11/20] htmldocs: Documentation/userspace-api/iommufd:174: ./include/uapi/linux/iommufd.h:117: WARNING: Unexpected indentation.
Date: Wed, 30 Nov 2022 20:03:34 -0400 [thread overview]
Message-ID: <Y4fvVvCbZgXxXg0J@nvidia.com> (raw)
In-Reply-To: <202212010331.21lwbBde-lkp@intel.com>
On Thu, Dec 01, 2022 at 03:57:59AM +0800, kernel test robot wrote:
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> Documentation/userspace-api/iommufd:174: ./include/uapi/linux/iommufd.h:117: WARNING: Unexpected indentation.
> >> Documentation/userspace-api/iommufd:174: ./include/uapi/linux/iommufd.h:119: WARNING: Block quote ends without a blank line; unexpected unindent.
>
This will fix it up:
diff --git a/include/uapi/linux/iommufd.h b/include/uapi/linux/iommufd.h
index de8d2d4f8bb604..98ebba80cfa1fc 100644
--- a/include/uapi/linux/iommufd.h
+++ b/include/uapi/linux/iommufd.h
@@ -114,9 +114,11 @@ struct iommu_iova_range {
* caller should allocate a larger output array and re-issue the ioctl.
*
* out_iova_alignment returns the minimum IOVA alignment that can be given
- * to IOMMU_IOAS_MAP/COPY. IOVA's must satisfy:
+ * to IOMMU_IOAS_MAP/COPY. IOVA's must satisfy::
+ *
* starting_iova % out_iova_alignment == 0
* (starting_iova + length) % out_iova_alignment == 0
+ *
* out_iova_alignment can be 1 indicating any IOVA is allowed. It cannot
* be higher than the system PAGE_SIZE.
*/
prev parent reply other threads:[~2022-12-01 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 19:57 [jgunthorpe:iommufd 11/20] htmldocs: Documentation/userspace-api/iommufd:174: ./include/uapi/linux/iommufd.h:117: WARNING: Unexpected indentation kernel test robot
2022-12-01 0:03 ` Jason Gunthorpe [this message]
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=Y4fvVvCbZgXxXg0J@nvidia.com \
--to=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nicolinc@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).