linux-renesas-soc.vger.kernel.org archive mirror
 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>,
	Magnus Damm <magnus.damm@gmail.com>,
	xu_shunji@hoperun.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 2/3] arm64: dts: renesas: hihope-common: Add pincontrol support to scif2/scif clock
Date: Thu, 6 Jun 2019 11:08:48 +0200	[thread overview]
Message-ID: <20190606090847.2hbiebue3k2ufjjy@verge.net.au> (raw)
In-Reply-To: <1559228266-16724-3-git-send-email-biju.das@bp.renesas.com>

On Thu, May 30, 2019 at 03:57:45PM +0100, Biju Das wrote:
> This patch adds pincontrol support to scif2/scif clock.
> 
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> Reviewed-by: Chris Paterson <Chris.Paterson2@renesas.com>

Thanks,
                                                                                applied for inclusion in v5.3.

  reply	other threads:[~2019-06-06  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 14:57 [PATCH 0/3] Add basic HiHope RZ/G2M board support Biju Das
2019-05-30 14:57 ` [PATCH 1/3] arm64: dts: renesas: Add HiHope RZ/G2M main " Biju Das
2019-06-06  9:08   ` Simon Horman
2019-06-06  9:50   ` Geert Uytterhoeven
2019-05-30 14:57 ` [PATCH 2/3] arm64: dts: renesas: hihope-common: Add pincontrol support to scif2/scif clock Biju Das
2019-06-06  9:08   ` Simon Horman [this message]
2019-06-06  9:50   ` Geert Uytterhoeven
2019-05-30 14:57 ` [PATCH 3/3] arm64: dts: renesas: Add HiHope RZ/G2M sub board support Biju Das
2019-06-06  9:09   ` Simon Horman
2019-06-06 10:01   ` Geert Uytterhoeven

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=20190606090847.2hbiebue3k2ufjjy@verge.net.au \
    --to=horms@verge.net.au \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.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=xu_shunji@hoperun.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).