From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux IOMMU <iommu@lists.linux.dev>,
Jonathan Corbet <corbet@lwn.net>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Samiullah Khawaja <skhawaja@google.com>,
Kevin Tian <kevin.tian@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>
Subject: Re: [PATCH 0/2] genpt documentation fixes
Date: Thu, 6 Nov 2025 09:12:06 -0400 [thread overview]
Message-ID: <20251106131206.GT1204670@ziepe.ca> (raw)
In-Reply-To: <20251106073845.36445-1-bagasdotme@gmail.com>
On Thu, Nov 06, 2025 at 02:38:43PM +0700, Bagas Sanjaya wrote:
> Hi,
>
> Here are fixes for two htmldocs warnings in generic radix page table
> documentation. The first one is reported in linux-next [1], and the
> second one is also found when making htmldocs locally to reproduce the
> former.
>
> Enjoy!
>
> [1]: https://lore.kernel.org/linux-next/20251106143925.578e411b@canb.auug.org.au/
>
> Bagas Sanjaya (2):
> Documentation: genpt: Don't use code block marker before iommu_amdv1.c
> include listing
> iommupt: Describe @bitnr parameter
>
> Documentation/driver-api/generic_pt.rst | 2 +-
> drivers/iommu/generic_pt/pt_common.h | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Thanks,
Jason
prev parent reply other threads:[~2025-11-06 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 7:38 [PATCH 0/2] genpt documentation fixes Bagas Sanjaya
2025-11-06 7:38 ` [PATCH 1/2] Documentation: genpt: Don't use code block marker before iommu_amdv1.c include listing Bagas Sanjaya
2025-11-06 23:49 ` Randy Dunlap
2025-11-06 7:38 ` [PATCH 2/2] iommupt: Describe @bitnr parameter Bagas Sanjaya
2025-11-06 23:48 ` Randy Dunlap
2025-11-07 0:35 ` Jason Gunthorpe
2025-11-07 5:14 ` Bagas Sanjaya
2025-11-06 13:12 ` 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=20251106131206.GT1204670@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bagasdotme@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=corbet@lwn.net \
--cc=iommu@lists.linux.dev \
--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