From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] Add R8A7743/SK-RZG1M board support
Date: Thu, 27 Oct 2016 09:06:15 +0200 [thread overview]
Message-ID: <20161027070615.GA7706@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWQegsEf_C=UGXpQiEAX0YQqy335teuvCZxBY6C=7QozA@mail.gmail.com>
On Wed, Oct 26, 2016 at 03:27:14PM +0200, Geert Uytterhoeven wrote:
> On Wed, Oct 26, 2016 at 3:23 PM, Sergei Shtylyov
> <sergei.shtylyov@cogentembedded.com> wrote:
> > On 10/26/2016 03:08 PM, Geert Uytterhoeven wrote:
> >>> Here's the set of 8 patches against Simon Horman's 'renesas.git'
> >>> repo's
> >>> 'renesas-devel-20161021-v4.9-rc1' tag. I'm adding the device tree support
> >>> for
> >>> the R8A7743-based SK-RZG1M board. The SoC is close to R8A7791 and the
> >>> board
> >>> seems identical to the R8A7791/Porter board. The device tree patches
> >>> depend on
> >>> the R8A7743 CPG/MSSR driver series just posted in order to compile and
> >>> work.
> >>
> >>
> >> They depend only on "[PATCH v3 1/2] ARM: shmobile: r8a7743: add CPG clock
> >> index macros" of that series, right?
> >>
> >> "[PATCH v3 2/2] clk: renesas: cpg-mssr: add R8A7743 support" is not
> >> needed,
> >
> > How would "clocks" props _work_ without this patch?
>
> Sorry, I was focusing too much on "compile"...
>
> Got my coke, switching brain to overdrive mode...
As we are talking about adding support for a new SoC I would be happy
to queue up code in my tree that compiles under the assumption that
in v4.10 the bits to make it run will appear in other branches.
prev parent reply other threads:[~2016-10-27 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 20:39 [PATCH v4 0/7] Add R8A7743/SK-RZG1M board support Sergei Shtylyov
2016-10-21 20:40 ` [PATCH v4 1/7] ARM: dts: r8a7743: initial SoC device tree Sergei Shtylyov
2016-10-21 20:41 ` [PATCH v4 2/7] ARM: dts: r8a7743: add SYS-DMAC support Sergei Shtylyov
2016-10-21 20:42 ` [PATCH v4 3/7] ARM: dts: r8a7743: add [H]SCIF{|A|B} support Sergei Shtylyov
2016-10-21 20:45 ` [PATCH v4 4/7] ARM: dts: r8a7743: add Ether support Sergei Shtylyov
2016-10-21 20:46 ` [PATCH v4 5/7] ARM: dts: r8a7743: add IRQC support Sergei Shtylyov
2016-10-21 20:47 ` [PATCH v4 6/7] ARM: dts: sk-rzg1m: initial device tree Sergei Shtylyov
2016-10-21 20:48 ` [PATCH v4 7/7] ARM: dts: sk-rzg1m: add Ether support Sergei Shtylyov
2016-10-26 12:08 ` [PATCH v4 0/7] Add R8A7743/SK-RZG1M board support Geert Uytterhoeven
2016-10-26 13:23 ` Sergei Shtylyov
2016-10-26 13:27 ` Geert Uytterhoeven
2016-10-27 7:06 ` 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=20161027070615.GA7706@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).