All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [PATCH 0/3] RZ/G2M SoC identification support
Date: Thu, 26 Jul 2018 15:27:08 +0200	[thread overview]
Message-ID: <20180726132707.aa7bm7macynuzeou@verge.net.au> (raw)
In-Reply-To: <1532447238-13486-1-git-send-email-biju.das@bp.renesas.com>

On Tue, Jul 24, 2018 at 04:47:15PM +0100, Biju Das wrote:
> This patch series aims to add SoC identification support 
> for RZ/G2M SoC. RZ/G2M SoC is similar to R-Car Gen3 M3-W SoC.
> 
> 
> Biju Das (3):
>   dt-bindings: arm: Document RZ/G2M SoC DT bindings
>   arm64: Add Renesas R8A774A1 support
>   soc: renesas: Identify RZ/G2M

Thanks, applied for v4.20.

      parent reply	other threads:[~2018-07-26 13:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 15:47 [PATCH 0/3] RZ/G2M SoC identification support Biju Das
2018-07-24 15:47 ` [PATCH 1/3] dt-bindings: arm: Document RZ/G2M SoC DT bindings Biju Das
2018-07-26 11:44   ` Geert Uytterhoeven
2018-07-31 22:14   ` Rob Herring
2018-07-24 15:47 ` [PATCH 2/3] arm64: Add Renesas R8A774A1 support Biju Das
2018-07-24 15:47   ` Biju Das
2018-07-26 11:44   ` Geert Uytterhoeven
2018-07-26 11:44     ` Geert Uytterhoeven
2018-07-24 15:47 ` [PATCH 3/3] soc: renesas: Identify RZ/G2M Biju Das
2018-07-26 11:47   ` Geert Uytterhoeven
2018-07-26 13:27 ` Simon Horman [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=20180726132707.aa7bm7macynuzeou@verge.net.au \
    --to=horms@verge.net.au \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@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.