Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
Date:   Thu, 20 Jul 2023 08:47:37 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From:   "Yajun Deng" <yajun.deng@linux.dev>
Message-ID: <25942dafbc7f52488a30c807b6322109539442cf@linux.dev>
TLS-Required: No
Subject: Re: [PATCH v3] dma-contiguous: support numa CMA for specified node
To:     "Christoph Hellwig" <hch@lst.de>
Cc:     corbet@lwn.net, hch@lst.de, m.szyprowski@samsung.com,
        robin.murphy@arm.com, akpm@linux-foundation.org,
        paulmck@kernel.org, catalin.marinas@arm.com, rdunlap@infradead.org,
        peterz@infradead.org, rostedt@goodmis.org, kim.phillips@amd.com,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        iommu@lists.linux.dev, linux-mm@kvack.org
In-Reply-To: <20230720082517.GA7057@lst.de>
References: <20230720082517.GA7057@lst.de>
 <20230712074758.1133272-1-yajun.deng@linux.dev>
Precedence: bulk

July 20, 2023 at 4:25 PM, "Christoph Hellwig" <hch@lst.de> wrote:


>=20
>=20It turns out this doesn't apply at all. Can you resend it against
> Linus' latest tree?
>

It's based on linux-next tree.

This patch should be after my other patch in linux-next tree.
a960925a6b23("dma-contiguous: support per-numa CMA for all architectures"=
).