All of lore.kernel.org
 help / color / mirror / Atom feed
From: Howard Yen <howardyen@google.com>
To: Christoph Hellwig <hch@lst.de>
Cc: 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: Mon, 19 Feb 2024 19:27:01 +0800	[thread overview]
Message-ID: <CAJDAHvYbMVCitf59OvKGQk+cWrHc9Sk7_20LSyssUOEeJGvbFg@mail.gmail.com> (raw)
In-Reply-To: <20240213055426.GA22451@lst.de>

On Tue, Feb 13, 2024 at 1:54 PM Christoph Hellwig <hch@lst.de> wrote:
>
> On Thu, Feb 08, 2024 at 03:28:05PM +0000, Howard Yen wrote:
> > Add support for multiple coherent rmems per device.
>
> Why?

Resend the message because the previous one contained some HTML.

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.


-- 
Regards,

Howard

      parent reply	other threads:[~2024-02-19 11:27 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
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 [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=CAJDAHvYbMVCitf59OvKGQk+cWrHc9Sk7_20LSyssUOEeJGvbFg@mail.gmail.com \
    --to=howardyen@google.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --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 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.