From: Joerg Roedel <joro@8bytes.org>
To: Matthew Rosato <mjrosato@linux.ibm.com>
Cc: will@kernel.org, robin.murphy@arm.com,
gerald.schaefer@linux.ibm.com, schnelle@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
svens@linux.ibm.com, borntraeger@linux.ibm.com, clg@redhat.com,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [PATCH v5 0/5] iommu/s390: support additional table regions
Date: Thu, 17 Apr 2025 16:43:38 +0200 [thread overview]
Message-ID: <aAETmiPYrK8_Toqm@8bytes.org> (raw)
In-Reply-To: <20250411202433.181683-1-mjrosato@linux.ibm.com>
On Fri, Apr 11, 2025 at 04:24:28PM -0400, Matthew Rosato wrote:
> Matthew Rosato (5):
> iommu/s390: set appropriate IOTA region type
> iommu/s390: support cleanup of additional table regions
> iommu/s390: support iova_to_phys for additional table regions
> iommu/s390: support map/unmap for additional table regions
> iommu/s390: allow larger region tables
>
> arch/s390/include/asm/pci_dma.h | 3 +
> drivers/iommu/s390-iommu.c | 345 ++++++++++++++++++++++++++++----
> 2 files changed, 314 insertions(+), 34 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2025-04-17 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 20:24 [PATCH v5 0/5] iommu/s390: support additional table regions Matthew Rosato
2025-04-11 20:24 ` [PATCH v5 1/5] iommu/s390: set appropriate IOTA region type Matthew Rosato
2025-04-11 20:24 ` [PATCH v5 2/5] iommu/s390: support cleanup of additional table regions Matthew Rosato
2025-04-11 20:24 ` [PATCH v5 3/5] iommu/s390: support iova_to_phys for " Matthew Rosato
2025-04-11 20:24 ` [PATCH v5 4/5] iommu/s390: support map/unmap " Matthew Rosato
2025-04-16 9:19 ` Niklas Schnelle
2025-04-11 20:24 ` [PATCH v5 5/5] iommu/s390: allow larger region tables Matthew Rosato
2025-04-16 9:35 ` Niklas Schnelle
2025-04-16 9:19 ` [PATCH v5 0/5] iommu/s390: support additional table regions Niklas Schnelle
2025-04-17 14:43 ` Joerg Roedel [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=aAETmiPYrK8_Toqm@8bytes.org \
--to=joro@8bytes.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=robin.murphy@arm.com \
--cc=schnelle@linux.ibm.com \
--cc=svens@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).