From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Nate Drude <nate.d@variscite.com>,
iommu@lists.linux.dev, Jonathan Corbet <corbet@lwn.net>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Borislav Petkov <bp@suse.de>,
"Paul E. McKenney" <paulmck@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Randy Dunlap <rdunlap@infradead.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Muchun Song <songmuchun@bytedance.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
eran.m@variscite.com
Subject: Re: [PATCH] dma-contiguous: add optional cma_name for cma= kernel parameter
Date: Fri, 23 Sep 2022 16:48:04 +0200 [thread overview]
Message-ID: <20220923144804.GA18477@lst.de> (raw)
In-Reply-To: <aa96eb55-4925-221f-1fb2-8226ea347c22@arm.com>
On Tue, Sep 13, 2022 at 11:45:17AM +0100, Robin Murphy wrote:
> If userspace expects the CMA heap driver to expose a consistent name for
> CMA heaps, shouldn't it be the CMA heap driver's responsibility to expose a
> consistent name for CMA heaps? Tinkering with the core CMA code doesn't
> feel like the right approach.
Agreed. In fact I think exposing this name in a uapi seems like a really
bad idea that is asking for a lot of trouble.
prev parent reply other threads:[~2022-09-23 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 16:38 [PATCH] dma-contiguous: add optional cma_name for cma= kernel parameter Nate Drude
2022-09-13 10:45 ` Robin Murphy
2022-09-23 14:48 ` Christoph Hellwig [this message]
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=20220923144804.GA18477@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=damien.lemoal@opensource.wdc.com \
--cc=eran.m@variscite.com \
--cc=iommu@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nate.d@variscite.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=songmuchun@bytedance.com \
/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