From: Jason Gunthorpe <jgg@nvidia.com>
To: fangyu.yu@linux.alibaba.com
Cc: joro@8bytes.org, alex@ghiti.fr, anup@brainfault.org,
aou@eecs.berkeley.edu, baolu.lu@linux.intel.com,
guoren@kernel.org, iommu@lists.linux.dev, kevin.tian@intel.com,
kvm-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, nutty.liu@hotmail.com,
palmer@dabbelt.com, pjw@kernel.org, robin.murphy@arm.com,
tjeznach@rivosinc.com, vasant.hegde@amd.com, will@kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: Re: [PATCH v3 0/2] iommu/riscv: Support Svpbmt memory types in generic_pt
Date: Tue, 12 May 2026 09:45:20 -0300 [thread overview]
Message-ID: <20260512124520.GH1116784@nvidia.com> (raw)
In-Reply-To: <20260512075339.18339-1-fangyu.yu@linux.alibaba.com>
On Tue, May 12, 2026 at 03:53:39PM +0800, fangyu.yu@linux.alibaba.com wrote:
> >> Fangyu Yu (2):
> >> iommu/riscv: Advertise Svpbmt support to generic page table
> >> iommupt: Encode IOMMU_MMIO/IOMMU_CACHE via RISC-V Svpbmt bits
> >>
> >> drivers/iommu/generic_pt/fmt/riscv.h | 11 ++++++++++-
> >> drivers/iommu/riscv/iommu.c | 2 ++
> >> include/linux/generic_pt/common.h | 4 ++++
> >> 3 files changed, 16 insertions(+), 1 deletion(-)
> >
> >Applied this one instead of v2.
>
> Thanks for the review and for applying this version. I’ve sent a v4
> update to fix the 32-bit build warning, so please use the v4 series
> going forward.
Since Joerg already applied it the normal thing is to send a fixup
patch to correct the bot warning
Jason
prev parent reply other threads:[~2026-05-12 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260417140746.97817-1-fangyu.yu@linux.alibaba.com>
2026-05-11 8:04 ` [PATCH v3 0/2] iommu/riscv: Support Svpbmt memory types in generic_pt Jörg Rödel
2026-05-12 7:53 ` fangyu.yu
2026-05-12 12:45 ` 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=20260512124520.GH1116784@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=baolu.lu@linux.intel.com \
--cc=fangyu.yu@linux.alibaba.com \
--cc=guoren@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=nutty.liu@hotmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tjeznach@rivosinc.com \
--cc=vasant.hegde@amd.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