From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Petr Tesařík" <petr@tesarici.cz>, "Christoph Hellwig" <hch@lst.de>
Cc: corbet@lwn.net, 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
Subject: Re: [PATCH v3] dma-contiguous: support numa CMA for specified node
Date: Fri, 21 Jul 2023 01:56:28 +0000 [thread overview]
Message-ID: <e2c15ec828daf2c1d4277e78859698929efe86b0@linux.dev> (raw)
In-Reply-To: <20230720142712.295834d0@meshulam.tesarici.cz>
July 20, 2023 at 8:27 PM, "Petr Tesařík" <petr@tesarici.cz> wrote:
>
> V Thu, 20 Jul 2023 13:54:08 +0200
> Christoph Hellwig <hch@lst.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
>
> >
> > dma patches really should be going through the DMA tree..
> >
>
> Indeed. The other patch was also sent to the iommu ML back in May. It's
> the thread where we were looking for Barry Song's current email address.
>
Thanks. This link shows what happened at that time:
https://lore.kernel.org/all/20230512094210.141540-1-yajun.deng@linux.dev/T/#u
> Petr T
>
next prev parent reply other threads:[~2023-07-21 1:56 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 1:56 ` Yajun Deng [this message]
2023-07-21 7:41 ` Christoph Hellwig
2023-07-20 16:59 ` Andrew Morton
2023-07-21 7:42 ` Christoph Hellwig
2023-07-24 0:42 ` Andrew Morton
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=e2c15ec828daf2c1d4277e78859698929efe86b0@linux.dev \
--to=yajun.deng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--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=petr@tesarici.cz \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.