From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Yajun Deng <yajun.deng@linux.dev>,
corbet@lwn.net, m.szyprowski@samsung.com, robin.murphy@arm.com,
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
Subject: Re: [PATCH v3] dma-contiguous: support numa CMA for specified node
Date: Fri, 21 Jul 2023 09:42:09 +0200 [thread overview]
Message-ID: <20230721074209.GA22859@lst.de> (raw)
In-Reply-To: <20230720095941.76803bbda5ad0c5103713d0c@linux-foundation.org>
On Thu, Jul 20, 2023 at 09:59:41AM -0700, Andrew Morton wrote:
> > 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.
Ah. And looking at the patch is isn't even pure dma but also has
a significant mm side. If you're fine with it I'll pick it up in
the dma-mapping tree in addition to the follow up.
next prev parent reply other threads:[~2023-07-21 7:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 7:47 [PATCH v3] dma-contiguous: support numa CMA for specified node Yajun Deng
2023-07-20 6:56 ` Christoph Hellwig
2023-07-20 8:25 ` Christoph Hellwig
2023-07-20 8:47 ` Yajun Deng
2023-07-20 11:54 ` Christoph Hellwig
2023-07-20 12:27 ` Petr Tesařík
2023-07-21 7:41 ` Christoph Hellwig
2023-07-20 16:59 ` Andrew Morton
2023-07-21 7:42 ` Christoph Hellwig [this message]
2023-07-24 0:42 ` Andrew Morton
2023-07-21 1:56 ` Yajun Deng
2023-07-31 16:02 ` Christoph Hellwig
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=20230721074209.GA22859@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=iommu@lists.linux.dev \
--cc=kim.phillips@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
--cc=yajun.deng@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).