From: Christoph Hellwig <hch@lst.de>
To: Howard Yen <howardyen@google.com>
Cc: Christoph Hellwig <hch@lst.de>,
m.szyprowski@samsung.com, robin.murphy@arm.com,
gregkh@linuxfoundation.org, andriy.shevchenko@linux.intel.com,
rafael@kernel.org, broonie@kernel.org, james@equiv.tech,
james.clark@arm.com, masahiroy@kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH v3] dma-coherent: add support for multi coherent rmems per dev
Date: Tue, 20 Feb 2024 06:52:41 +0100 [thread overview]
Message-ID: <20240220055241.GA7554@lst.de> (raw)
In-Reply-To: <CAJDAHvZGnzKPLaovRcq_Os1Fcixp2o1kY9GFV8VXztrmKahejQ@mail.gmail.com>
On Mon, Feb 19, 2024 at 07:12:18PM +0800, Howard Yen wrote:
> I tried to upload the patch to support multiple coherent rmems per device
> because in some system, the primary memory space for the device might
> be limited, so that add multiple coherent rmems support per device to satisfy
> the scenario.
I'm not sure what the means.
If you have non-trivial patches you really need to explain why you're
doing in detail as you need to convince maintainers that it is useful.
next prev parent reply other threads:[~2024-02-20 5:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 15:28 [PATCH v3] dma-coherent: add support for multi coherent rmems per dev Howard Yen
2024-02-08 18:02 ` Andy Shevchenko
2024-02-19 11:29 ` Howard Yen
2024-02-13 5:54 ` Christoph Hellwig
2024-02-19 11:12 ` Howard Yen
2024-02-20 5:52 ` Christoph Hellwig [this message]
2024-02-21 9:27 ` Howard Yen
2024-02-23 6:37 ` Christoph Hellwig
2024-02-27 13:39 ` Howard Yen
2024-02-27 14:31 ` Robin Murphy
2024-03-04 9:47 ` Howard Yen
2024-02-19 11:27 ` Howard Yen
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=20240220055241.GA7554@lst.de \
--to=hch@lst.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=howardyen@google.com \
--cc=iommu@lists.linux.dev \
--cc=james.clark@arm.com \
--cc=james@equiv.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=masahiroy@kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.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