All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] mmc: renesas_sdhi_internal_dmac: add R8A77980 to whitelist
Date: Mon, 23 Apr 2018 11:18:05 +0200	[thread overview]
Message-ID: <CAPDyKFrBJzqwj-NhuopwTSjBeX1U=zYdG4J703h93YCPgRK8Rg@mail.gmail.com> (raw)
In-Reply-To: <66c0b103-ed6e-36e0-74a6-9809ba55939c@cogentembedded.com>

On 19 April 2018 at 22:07, Sergei Shtylyov
<sergei.shtylyov@cogentembedded.com> wrote:
> I've successfully tested eMMC on R8A77980/Condor. R8A77980 has a single
> SDHI core anyway, so can't be a subject of the known RX DMA errata...
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

Thanks, applied for next!

Kind regards
Uffe

>
> ---
> This patch is against the 'next' branch of Ulf Hansson's 'mmc.git' repo.
>
>  drivers/mmc/host/renesas_sdhi_internal_dmac.c |    1 +
>  1 file changed, 1 insertion(+)
>
> Index: mmc/drivers/mmc/host/renesas_sdhi_internal_dmac.c
> ===================================================================
> --- mmc.orig/drivers/mmc/host/renesas_sdhi_internal_dmac.c
> +++ mmc/drivers/mmc/host/renesas_sdhi_internal_dmac.c
> @@ -276,6 +276,7 @@ static const struct soc_device_attribute
>         /* generic ones */
>         { .soc_id = "r8a7795" },
>         { .soc_id = "r8a7796" },
> +       { .soc_id = "r8a77980" },
>         { .soc_id = "r8a77995" },
>         { /* sentinel */ }
>  };

      parent reply	other threads:[~2018-04-23  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 20:07 [PATCH] mmc: renesas_sdhi_internal_dmac: add R8A77980 to whitelist Sergei Shtylyov
2018-04-19 20:09 ` Wolfram Sang
2018-04-20  7:08   ` Ulf Hansson
2018-04-20  8:36     ` Sergei Shtylyov
2018-04-23  9:18 ` Ulf Hansson [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='CAPDyKFrBJzqwj-NhuopwTSjBeX1U=zYdG4J703h93YCPgRK8Rg@mail.gmail.com' \
    --to=ulf.hansson@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=wsa+renesas@sang-engineering.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.