From: Christoph Hellwig <hch@lst•de>
To: Barry Song <song.bao.hua@hisilicon•com>
Cc: catalin.marinas@arm•com, Mike Rapoport <rppt@linux•ibm.com>,
Steve Capper <steve.capper@arm•com>,
robin.murphy@arm•com, linuxarm@huawei•com,
linux-kernel@vger•kernel.org, iommu@lists•linux-foundation.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse•de>,
prime.zeng@hisilicon•com, ganapatrao.kulkarni@cavium•com,
Andrew Morton <akpm@linux-foundation•org>,
huangdaode@huawei•com, will@kernel•org, hch@lst•de,
linux-arm-kernel@lists•infradead.org, m.szyprowski@samsung•com
Subject: Re: [PATCH v4 2/2] arm64: mm: reserve per-numa CMA to localize coherent dma buffers
Date: Tue, 28 Jul 2020 13:53:02 +0200 [thread overview]
Message-ID: <20200728115302.GB793@lst.de> (raw)
In-Reply-To: <20200723131344.41472-3-song.bao.hua@hisilicon.com>
Looks ok to me, but before I pick the series up in the dma-mapping tree
I really want an ACK from the arm64 maintainers.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-28 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 13:13 [PATCH v4 0/2] make dma_alloc_coherent NUMA-aware by per-NUMA CMA Barry Song
2020-07-23 13:13 ` [PATCH v4 1/2] dma-direct: provide the ability to reserve per-numa CMA Barry Song
2020-07-28 11:52 ` Christoph Hellwig
2020-07-28 12:19 ` Song Bao Hua (Barry Song)
2020-07-28 12:22 ` Christoph Hellwig
2020-07-29 11:21 ` Song Bao Hua (Barry Song)
2020-07-23 13:13 ` [PATCH v4 2/2] arm64: mm: reserve per-numa CMA to localize coherent dma buffers Barry Song
2020-07-28 11:53 ` 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=20200728115302.GB793@lst.de \
--to=hch@lst$(echo .)de \
--cc=akpm@linux-foundation$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=ganapatrao.kulkarni@cavium$(echo .)com \
--cc=huangdaode@huawei$(echo .)com \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxarm@huawei$(echo .)com \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=nsaenzjulienne@suse$(echo .)de \
--cc=prime.zeng@hisilicon$(echo .)com \
--cc=robin.murphy@arm$(echo .)com \
--cc=rppt@linux$(echo .)ibm.com \
--cc=song.bao.hua@hisilicon$(echo .)com \
--cc=steve.capper@arm$(echo .)com \
--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