From: Nicolas Saenz Julienne <nsaenzjulienne@suse•de>
To: Catalin Marinas <catalin.marinas@arm•com>
Cc: linux-s390@vger•kernel.org, mbrugger@suse•com,
Vasily Gorbik <gor@linux•ibm.com>,
wahrenst@gmx•net, Michael Ellerman <mpe@ellerman•id.au>,
Will Deacon <will@kernel•org>,
linuxppc-dev@lists•ozlabs.org,
Heiko Carstens <heiko.carstens@de•ibm.com>,
linux-kernel@vger•kernel.org,
ChristophHellwig <hch@infradead•org>,
Christian Borntraeger <borntraeger@de•ibm.com>,
iommu@lists•linux-foundation.org, f.fainelli@gmail•com,
bcm-kernel-feedback-list@broadcom•com,
linux-rpi-kernel@lists•infradead.org,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
Robin Murphy <robin.murphy@arm•com>,
linux-arm-kernel@lists•infradead.org,
Marek Szyprowski <m.szyprowski@samsung•com>
Subject: Re: [PATCH RFC 1/5] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable
Date: Thu, 31 Oct 2019 18:26:10 +0100 [thread overview]
Message-ID: <9c051b0f2d89baa36fd3d3669a107f549c310d49.camel@suse.de> (raw)
In-Reply-To: <20191031133831.GA21509@infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 1091 bytes --]
On Thu, 2019-10-31 at 06:38 -0700, Christoph Hellwig wrote:
> On Thu, Oct 31, 2019 at 11:30:36AM +0100, Nicolas Saenz Julienne wrote:
> > On Wed, 2019-10-30 at 14:49 -0700, Christoph Hellwig wrote:
> > > On Mon, Oct 14, 2019 at 08:31:03PM +0200, Nicolas Saenz Julienne wrote:
> > > > Some architectures, notably ARM, are interested in tweaking this
> > > > depending on their runtime DMA addressing limitations.
> > > >
> > > > Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse•de>
> > >
> > > Do you want me to pick this up for the 5.5 dma-mapping tree, or do you
> > > want me to wait for the rest to settle?
> >
> > I'd say take it, this will be ultimately needed once we push forward with
> > ARM.
>
> Can you resend a version that applies against 5.4-rc? The current one
> has conflicts in the arm64 code.
Hi Catalin,
would you mind taking this patch on top of the arm64 ZONE_DMA series?
I tried to go though Christoph's tree but it ultimately clashes with the
ZONE_DMA series. It's simpler to apply it on top of your tree.
Regrads,
Nicolas
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-31 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 18:31 [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support Nicolas Saenz Julienne
2019-10-14 18:31 ` [PATCH RFC 1/5] dma/direct: turn ARCH_ZONE_DMA_BITS into a variable Nicolas Saenz Julienne
2019-10-30 21:49 ` Christoph Hellwig
2019-10-31 10:30 ` Nicolas Saenz Julienne
2019-10-31 13:38 ` Christoph Hellwig
2019-10-31 17:26 ` Nicolas Saenz Julienne [this message]
2019-10-14 18:31 ` [PATCH RFC 2/5] ARM: introduce arm_dma_direct Nicolas Saenz Julienne
2019-10-15 10:04 ` Christoph Hellwig
2019-10-14 18:31 ` [PATCH RFC 3/5] ARM: let machines select dma-direct over arch's DMA implementation Nicolas Saenz Julienne
2019-10-14 18:31 ` [PATCH RFC 4/5] dma/direct: check for overflows in ARM's dma_capable() Nicolas Saenz Julienne
2019-10-15 10:23 ` Christoph Hellwig
2019-10-15 13:07 ` Nicolas Saenz Julienne
2019-10-14 18:31 ` [PATCH RFC 5/5] ARM: bcm2711: use dma-direct Nicolas Saenz Julienne
2019-10-14 20:59 ` [PATCH RFC 0/5] ARM: Raspberry Pi 4 DMA support Catalin Marinas
2019-10-15 7:48 ` Nicolas Saenz Julienne
2019-10-15 17:46 ` Catalin Marinas
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=9c051b0f2d89baa36fd3d3669a107f549c310d49.camel@suse.de \
--to=nsaenzjulienne@suse$(echo .)de \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=gor@linux$(echo .)ibm.com \
--cc=hch@infradead$(echo .)org \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rpi-kernel@lists$(echo .)infradead.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=mbrugger@suse$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
--cc=robin.murphy@arm$(echo .)com \
--cc=wahrenst@gmx$(echo .)net \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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