From: Christoph Hellwig <hch@lst.de>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, "Petr Tesařík" <petr@tesarici.cz>,
"Ramon Fried" <ramon@neureality.ai>,
"Elad Nachman" <enachman@marvell.com>
Subject: Re: [PATCH v6 RESED 0/2] dma: support DMA zone starting above 4GB
Date: Thu, 22 Aug 2024 06:18:46 +0200 [thread overview]
Message-ID: <20240822041846.GA856@lst.de> (raw)
In-Reply-To: <cover.1723359916.git.baruch@tkos.co.il>
Thanks,
applied to the dma-mapping tree for Linux 6.12.
prev parent reply other threads:[~2024-08-22 4:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 7:09 [PATCH v6 RESED 0/2] dma: support DMA zone starting above 4GB Baruch Siach
2024-08-11 7:09 ` Baruch Siach
2024-08-11 7:09 ` [PATCH v6 RESED 1/2] dma: replace zone_dma_bits by zone_dma_limit Baruch Siach
2024-08-11 7:09 ` Baruch Siach
2024-08-12 5:52 ` Petr Tesarik
2024-08-12 5:52 ` Petr Tesarik
2024-08-12 11:22 ` Catalin Marinas
2024-08-16 11:52 ` Will Deacon
2024-08-16 14:37 ` Petr Tesařík
2024-08-26 19:28 ` Marek Szyprowski
2024-08-26 19:28 ` Marek Szyprowski
2024-08-27 4:52 ` Baruch Siach
2024-08-27 4:52 ` Baruch Siach
2024-08-27 6:14 ` Marek Szyprowski
2024-08-27 6:14 ` Marek Szyprowski
2024-08-27 7:03 ` Baruch Siach
2024-08-27 7:03 ` Baruch Siach
2024-08-27 7:46 ` Marek Szyprowski
2024-08-27 7:46 ` Marek Szyprowski
2024-08-29 13:42 ` Neil Armstrong
2024-08-29 14:38 ` Robin Murphy
2024-08-29 14:54 ` neil.armstrong
2024-08-11 7:09 ` [PATCH v6 RESED 2/2] arm64: support DMA zone above 4GB Baruch Siach
2024-08-11 7:09 ` Baruch Siach
2024-08-12 5:54 ` Petr Tesarik
2024-08-12 5:54 ` Petr Tesarik
2024-08-22 4:18 ` 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=20240822041846.GA856@lst.de \
--to=hch@lst.de \
--cc=baruch@tkos.co.il \
--cc=catalin.marinas@arm.com \
--cc=enachman@marvell.com \
--cc=iommu@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=petr@tesarici.cz \
--cc=ramon@neureality.ai \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.