[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230720095941.76803bbda5ad0c5103713d0c@linux-foundation.org>
Date: Thu, 20 Jul 2023 09:59:41 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christoph Hellwig <hch@....de>
Cc: Yajun Deng <yajun.deng@...ux.dev>, corbet@....net,
m.szyprowski@...sung.com, robin.murphy@....com, paulmck@...nel.org,
catalin.marinas@....com, rdunlap@...radead.org,
peterz@...radead.org, rostedt@...dmis.org, kim.phillips@....com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
iommu@...ts.linux.dev, linux-mm@...ck.org
Subject: Re: [PATCH v3] dma-contiguous: support numa CMA for specified node
On Thu, 20 Jul 2023 13:54:08 +0200 Christoph Hellwig <hch@....de> wrote:
> On Thu, Jul 20, 2023 at 08:47:37AM +0000, Yajun Deng wrote:
> > 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").
>
> Where did this land? dma patches really should be going through
> the DMA tree..
It's in mm-unstable with a note "hch" :)
I'll drop it.
Powered by blists - more mailing lists