From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Christoph Hellwig" <hch@lst.de>
Cc: corbet@lwn.net, catalin.marinas@arm.com, will@kernel.org,
m.szyprowski@samsung.com, robin.murphy@arm.com,
paulmck@kernel.org, bp@suse.de, akpm@linux-foundation.org,
peterz@infradead.org, rdunlap@infradead.org,
kim.phillips@amd.com, rostedt@goodmis.org,
thunder.leizhen@huawei.com, ardb@kernel.org, bhe@redhat.com,
anshuman.khandual@arm.com, song.bao.hua@hisilicon.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev
Subject: Re: [PATCH] dma-contiguous: support per-numa CMA for all architectures
Date: Mon, 15 May 2023 11:23:27 +0000 [thread overview]
Message-ID: <055f964384a2bb4ba51c64a0be6072c9@linux.dev> (raw)
In-Reply-To: <20230515094955.GB23880@lst.de>
May 15, 2023 5:49 PM, "Christoph Hellwig" <hch@lst.de> wrote:
> This looks fine to me. Can you please work with Barry to make sure
> the slight different place of the initcall doesn't break anything
> for his setup? I doubt it would, but I'd rather have a Tested-by:
> tag.
Barry's email is no longer in use. I can't reach him.
WARNING: multiple messages have this Message-ID (diff)
From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Christoph Hellwig" <hch@lst.de>
Cc: corbet@lwn.net, catalin.marinas@arm.com, will@kernel.org,
m.szyprowski@samsung.com, robin.murphy@arm.com,
paulmck@kernel.org, bp@suse.de, akpm@linux-foundation.org,
peterz@infradead.org, rdunlap@infradead.org,
kim.phillips@amd.com, rostedt@goodmis.org,
thunder.leizhen@huawei.com, ardb@kernel.org, bhe@redhat.com,
anshuman.khandual@arm.com, song.bao.hua@hisilicon.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev
Subject: Re: [PATCH] dma-contiguous: support per-numa CMA for all architectures
Date: Mon, 15 May 2023 11:23:27 +0000 [thread overview]
Message-ID: <055f964384a2bb4ba51c64a0be6072c9@linux.dev> (raw)
In-Reply-To: <20230515094955.GB23880@lst.de>
May 15, 2023 5:49 PM, "Christoph Hellwig" <hch@lst.de> wrote:
> This looks fine to me. Can you please work with Barry to make sure
> the slight different place of the initcall doesn't break anything
> for his setup? I doubt it would, but I'd rather have a Tested-by:
> tag.
Barry's email is no longer in use. I can't reach him.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-15 11:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 9:42 [PATCH] dma-contiguous: support per-numa CMA for all architectures Yajun Deng
2023-05-12 21:08 ` Andrew Morton
2023-05-15 9:49 ` Christoph Hellwig
2023-05-15 9:49 ` Christoph Hellwig
2023-05-15 11:23 ` Yajun Deng [this message]
2023-05-15 11:23 ` Yajun Deng
2023-05-15 11:38 ` Petr Tesařík
2023-05-15 11:38 ` Petr Tesařík
2023-05-16 1:57 ` Yajun Deng
2023-05-16 1:57 ` Yajun Deng
2023-06-24 0:40 ` Andrew Morton
2023-06-24 0:40 ` Andrew Morton
2023-06-25 7:30 ` Yajun Deng
2023-06-25 7:30 ` Yajun Deng
2023-06-26 5:32 ` Barry Song
2023-06-26 5:32 ` Barry Song
2023-06-29 1:41 ` Yicong Yang
2023-06-29 1:41 ` Yicong Yang
2023-05-16 1:55 ` Yajun Deng
2023-05-16 1:55 ` Yajun Deng
2023-07-31 16:02 ` Christoph Hellwig
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=055f964384a2bb4ba51c64a0be6072c9@linux.dev \
--to=yajun.deng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=bp@suse.de \
--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-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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=song.bao.hua@hisilicon.com \
--cc=thunder.leizhen@huawei.com \
--cc=will@kernel.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.