devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chris Paterson <chris.paterson2@renesas.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Biju Das <biju.das@bp.renesas.com>,
	Linux MMC List <linux-mmc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/3] ARM: dts: r8a7743: Add MMCIF0 support
Date: Thu, 13 Jul 2017 09:59:01 +0200	[thread overview]
Message-ID: <20170713075900.GH5580@verge.net.au> (raw)
In-Reply-To: <CAMuHMdV9V56kU8PtZb3jHwQeocj2_uUDYN3D=g2ZxHGN0cSbhQ@mail.gmail.com>

On Wed, Jul 12, 2017 at 01:21:20PM +0200, Geert Uytterhoeven wrote:
> On Wed, Jul 12, 2017 at 12:03 PM, Chris Paterson
> <chris.paterson2@renesas.com> wrote:
> > Add the MMCIF0 device to the r8a7743 device tree.
> >
> > Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>
> 
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Thanks, applied for v4.14.

  reply	other threads:[~2017-07-13  7:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 10:03 [PATCH 0/3] Add MMCIF0 support for r8a7743/iwg20m Chris Paterson
2017-07-12 10:03 ` [PATCH 1/3] dt-bindings: mmc: sh_mmcif: Document r8a7743 DT bindings Chris Paterson
2017-07-12 11:20   ` Geert Uytterhoeven
2017-07-13  7:54     ` Simon Horman
2017-07-13  8:00       ` Geert Uytterhoeven
2017-07-13  8:07         ` Simon Horman
2017-07-13 10:06   ` Ulf Hansson
2017-07-12 10:03 ` [PATCH 2/3] ARM: dts: r8a7743: Add MMCIF0 support Chris Paterson
2017-07-12 11:21   ` Geert Uytterhoeven
2017-07-13  7:59     ` Simon Horman [this message]
2017-07-12 10:03 ` [PATCH 3/3] ARM: dts: iwg20m: " Chris Paterson
     [not found]   ` <1499853805-5915-4-git-send-email-chris.paterson2-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-07-12 11:52     ` Geert Uytterhoeven
2017-07-13  8:02       ` Simon Horman
     [not found]         ` <20170713080228.GI5580-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-07-13  8:12           ` Simon Horman
2017-07-13  9:28             ` Chris Paterson
2017-07-13  0:25   ` kbuild test robot
     [not found]     ` <201707130850.0py1QazG%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-07-13  7:54       ` Simon Horman
     [not found]         ` <20170713075414.GF5580-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-07-13  8:46           ` [kbuild-all] " Ye Xiaolong
2017-07-13 15:39   ` [PATCH v2] " Chris Paterson
2017-07-13 16:31     ` Geert Uytterhoeven
     [not found]       ` <CAMuHMdV2f1oyi9dNGdGmqx7x7RNk10jomKQ4jHJ9wXNSEBKtNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-14  7:33         ` Simon Horman

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=20170713075900.GH5580@verge.net.au \
    --to=horms@verge.net.au \
    --cc=biju.das@bp.renesas.com \
    --cc=chris.paterson2@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=ulf.hansson@linaro.org \
    /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).