devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: linux-renesas-soc@vger.kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	magnus.damm@gmail.com, linux@arm.linux.org.uk,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Add R8A7792 I2C support
Date: Mon, 25 Jul 2016 11:09:48 +0900	[thread overview]
Message-ID: <20160725020947.GI12825@verge.net.au> (raw)
In-Reply-To: <17288006.ERHB6654v5@wasted.cogentembedded.com>

On Sat, Jul 23, 2016 at 10:15:56PM +0300, Sergei Shtylyov wrote:
> Hello.
> 
>    Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
> 'renesas-devel-20160722-v4.7-rc7' tag plus the SDHI/I2C patches just posted.
> We're adding the R8A7792 VIN clocks and device nodes. The patches have been
> tested on the Blanche board with the switches set to the HDMI input mode...
> 
> [1/2] ARM: dts: r8a7792: add VIN clocks
> [2/2] ARM: dts: r8a7792: add VIN support

Thanks, I have queued these up for v4.9.

  parent reply	other threads:[~2016-07-25  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 19:15 [PATCH 0/2] Add R8A7792 I2C support Sergei Shtylyov
2016-07-23 19:16 ` [PATCH 1/2] ARM: dts: r8a7792: add VIN clocks Sergei Shtylyov
     [not found]   ` <1477310.o5B8uhf3mT-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2016-08-08 12:42     ` Geert Uytterhoeven
2016-07-23 19:17 ` [PATCH 2/2] ARM: dts: r8a7792: add VIN support Sergei Shtylyov
2016-08-08 12:46   ` Geert Uytterhoeven
2016-07-25  2:09 ` Simon Horman [this message]
2016-07-25 10:40   ` [PATCH 0/2] Add R8A7792 I2C support Sergei Shtylyov
  -- strict thread matches above, loose matches on Subject: below --
2016-07-23 18:47 Sergei Shtylyov

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=20160725020947.GI12825@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).