linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: dts: r8a7793: add CAN to device tree
Date: Tue, 15 Mar 2016 17:02:32 +0900	[thread overview]
Message-ID: <20160315080232.GD6912@verge.net.au> (raw)
In-Reply-To: <SG2PR06MB10386A43CDCBE656A3ACBE12C3890@SG2PR06MB1038.apcprd06.prod.outlook.com>

On Tue, Mar 15, 2016 at 07:09:23AM +0000, Ramesh Shanmugasundaram wrote:
> Hi Simon,
> 
> > Subject: [PATCH v2 0/2] ARM: dts: r8a7793: add CAN to device tree
> 
> r8a7794?

Yes, my bad.

> > 
> > Hi,
> > 
> > this short series adds CAN clocks and nodes to the r8a7794 device tree.
> > 
> > I am not aware of an r8a7794 board that exposes CAN - neither the alt nor
> > the silk board appear to - and thus am unsure of a way to test these
> > changes.  However, they are based on what is present for the r8a7791 SoC
> > and I am unable to find a difference in the SoC documentation.
> > 
> > This series is similar to a similar series I posted for the r8a7794 in
> > January.
> > 
> > Based on renesas-devel-20160311-v4.5-rc7.
> > 
> > Changes in v2
> > * Correct clock node names
> > * Add MSTP9 clocks
> > * Omit clock-output-names property from new nodes
> 
> Acked-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
> 
> for this series.

Thanks

  reply	other threads:[~2016-03-15  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15  0:26 [PATCH v2 0/2] ARM: dts: r8a7793: add CAN to device tree Simon Horman
2016-03-15  0:26 ` [PATCH v2 1/2] ARM: dts: r8a7794: add CAN clocks " Simon Horman
2016-03-15  8:21   ` Geert Uytterhoeven
2016-03-15  0:26 ` [PATCH v2 2/2] ARM: dts: r8a7794: add CAN nodes " Simon Horman
2016-03-15  7:09 ` [PATCH v2 0/2] ARM: dts: r8a7793: add CAN " Ramesh Shanmugasundaram
2016-03-15  8:02   ` Simon Horman [this message]
2016-03-16  0:10     ` Simon Horman
  -- strict thread matches above, loose matches on Subject: below --
2016-03-16  1:52 Simon Horman
2016-03-17  2:09 ` 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=20160315080232.GD6912@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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).