From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Joerg Roedel <joro@8bytes.org>, Christoph Hellwig <hch@lst.de>,
Vineet Gupta <vgupta@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
David Woodhouse <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
iommu@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/7] dma-mapping: Simplify arch_setup_dma_ops()
Date: Wed, 6 Mar 2024 13:10:50 +0100 [thread overview]
Message-ID: <20240306121050.GA8863@lst.de> (raw)
In-Reply-To: <6af5e7da-08ba-4fc7-8e57-863377182142@arm.com>
On Wed, Mar 06, 2024 at 12:02:41PM +0000, Robin Murphy wrote:
> Are either of you happy to pick this series up now that we have Hanjun's
> acks for the IORT parts? As it stands it still applies cleanly to both
> iommu/next and dma/for-next. I do have some followup IOMMU patches prepared
> already (continuing to delete more code, yay!), but I don't want to get too
> far ahead of myself.
I expected this to go in through the iommu tree. But if Joerg want
the series (or part of it) to go through the dma-mapping tree I'd
be happy to pick it up ASAP.
prev parent reply other threads:[~2024-03-06 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 16:49 [PATCH v3 0/7] dma-mapping: Simplify arch_setup_dma_ops() Robin Murphy
2024-02-09 16:49 ` [PATCH v3 1/7] OF: Retire dma-ranges mask workaround Robin Murphy
2024-02-09 16:49 ` [PATCH v3 2/7] OF: Simplify DMA range calculations Robin Murphy
2024-02-09 16:50 ` [PATCH v3 3/7] ACPI/IORT: Handle memory address size limits as limits Robin Murphy
2024-02-24 11:43 ` Hanjun Guo
2024-02-09 16:50 ` [PATCH v3 4/7] dma-mapping: Add helpers for dma_range_map bounds Robin Murphy
2024-02-24 11:47 ` Hanjun Guo
2024-02-09 16:50 ` [PATCH v3 5/7] iommu/dma: Make limit checks self-contained Robin Murphy
2024-02-09 16:50 ` [PATCH v3 6/7] iommu/dma: Centralise iommu_setup_dma_ops() Robin Murphy
2024-02-10 11:27 ` Baolu Lu
2024-03-08 20:37 ` Jason Gunthorpe
2024-02-09 16:50 ` [PATCH v3 7/7] dma-mapping: Simplify arch_setup_dma_ops() Robin Murphy
2024-02-09 19:37 ` Michael Kelley
2024-03-08 20:37 ` Jason Gunthorpe
2024-02-24 11:32 ` [PATCH v3 0/7] " Hanjun Guo
2024-03-06 12:02 ` Robin Murphy
2024-03-06 12:10 ` Christoph Hellwig [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=20240306121050.GA8863@lst.de \
--to=hch@lst.de \
--cc=aou@eecs.berkeley.edu \
--cc=baolu.lu@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=frowand.list@gmail.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=guohanjun@huawei.com \
--cc=haiyangz@microsoft.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kernel@xen0n.name \
--cc=kys@microsoft.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lpieralisi@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mjrosato@linux.ibm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=schnelle@linux.ibm.com \
--cc=sudeep.holla@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tsbogend@alpha.franken.de \
--cc=vgupta@kernel.org \
--cc=wei.liu@kernel.org \
--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).