archive mirror
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <>
To: Christoph Hellwig <>, Wolfram Sang <>
Cc: "" <>,
	"" <>,
Subject: RE: [PATCH v4 0/3] mmc: renesas_sdhi: improve performance by changing max_segs
Date: Tue, 4 Jun 2019 01:27:37 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Christoph, Wolfram,

> From: Christoph Hellwig, Sent: Monday, June 3, 2019 10:12 PM
> On Mon, Jun 03, 2019 at 02:57:01PM +0200, Wolfram Sang wrote:
> > Yes, dropping my rev on patch 3 is a good thing to do. I added Christoph
> > to the CC list because he gave valuable input last time.
> Assuming iommu merging in a driver using the DMA API is always bogus
> as mentioned last time.  As this cover letter don't seem to include
> any higher level DMA subsystem or block changes I'll stick to my NAK.

Thank you very much for your reply again. I understood this patch series is NAK.
I'll continue to investigate DMA or block subsystem to achieve this. (I'm not sure
I can succeed or not though...)

Best regards,
Yoshihiro Shimoda

      reply	other threads:[~2019-06-04  1:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 11:16 [PATCH v4 0/3] mmc: renesas_sdhi: improve performance by changing max_segs Yoshihiro Shimoda
2019-05-31 11:16 ` [PATCH v4 1/3] mmc: tmio: No memory size limitation if runs on IOMMU Yoshihiro Shimoda
2019-05-31 11:16 ` [PATCH v4 2/3] mmc: tmio: Add a definition for default max_segs Yoshihiro Shimoda
2019-05-31 11:16 ` [PATCH v4 3/3] mmc: renesas_sdhi: use multiple segments if possible Yoshihiro Shimoda
2019-06-03 12:57 ` [PATCH v4 0/3] mmc: renesas_sdhi: improve performance by changing max_segs Wolfram Sang
2019-06-03 13:11   ` Christoph Hellwig
2019-06-04  1:27     ` Yoshihiro Shimoda [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).