[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230721074115.GA22796@lst.de>
Date: Fri, 21 Jul 2023 09:41:15 +0200
From: Christoph Hellwig <hch@....de>
To: Petr Tesařík <petr@...arici.cz>
Cc: Christoph Hellwig <hch@....de>, Yajun Deng <yajun.deng@...ux.dev>,
corbet@....net, m.szyprowski@...sung.com, robin.murphy@....com,
akpm@...ux-foundation.org, 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, Jul 20, 2023 at 02:27:12PM +0200, Petr Tesařík wrote:
> V Thu, 20 Jul 2023 13:54:08 +0200
> Christoph Hellwig <hch@....de> napsáno:
>
> > 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?
>
> Well... in the linux-next tree:
>
> https://www.kernel.org/doc/man-pages/linux-next.html
Well, linux-next just pulls in maintainer trees. So nothing lands
directly in linux-next. But it looks like Andrew already cleared up
the confusion.
Powered by blists - more mailing lists