linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Christoph Hellwig <hch@infradead.org>,
	ulf.hansson@linaro.org, wsa+renesas@sang-engineering.com,
	linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v4 0/3] mmc: renesas_sdhi: improve performance by changing max_segs
Date: Mon, 3 Jun 2019 06:11:51 -0700	[thread overview]
Message-ID: <20190603131151.GA6147@infradead.org> (raw)
In-Reply-To: <20190603125701.jkmpkvctrtlj2io7@ninjato>

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.

  reply	other threads:[~2019-06-03 13:11 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 [this message]
2019-06-04  1:27     ` Yoshihiro Shimoda

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=20190603131151.GA6147@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@the-dreams.de \
    --cc=yoshihiro.shimoda.uh@renesas.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;
as well as URLs for NNTP newsgroup(s).