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 DU support
Date: Tue, 9 Aug 2016 14:32:31 +0200 [thread overview]
Message-ID: <20160809123228.GA5878@verge.net.au> (raw)
In-Reply-To: <4a413062-d7f4-166a-f915-01803bddf441@cogentembedded.com>
On Fri, Aug 05, 2016 at 09:28:59PM +0300, Sergei Shtylyov wrote:
> On 08/05/2016 09:24 PM, Sergei Shtylyov wrote:
>
> > Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
> >'renesas-devel-20160725-v4.7-rc7' tag. We're adding the R8A7792 DU clocks and
> >device nodes. They have been tested on the Blanche board -- I'm not posting the
> >Blanche patch only because it also has some strange interaction with the
> >Ethernet chip, so that NFS root can't work anymore...
>
> Forgot to mention that the patch #2 depends on the R8A7792 DU driver
> patch posted last night.
Thanks.
The driver changes look line an incremental update to what is already done
for other R-Car Gen2 SoCs. And I am assuming that applying these patches
without the driver change is harmless - the driver just won't be
initialised until both the driver and DTS changes are present.
With the above reasoning I have queued up these patches with Geert's
reviewed-by tag. Please let me know if that is not desirable for some
reason.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add R8A7792 DU support
Date: Tue, 9 Aug 2016 14:32:31 +0200 [thread overview]
Message-ID: <20160809123228.GA5878@verge.net.au> (raw)
In-Reply-To: <4a413062-d7f4-166a-f915-01803bddf441@cogentembedded.com>
On Fri, Aug 05, 2016 at 09:28:59PM +0300, Sergei Shtylyov wrote:
> On 08/05/2016 09:24 PM, Sergei Shtylyov wrote:
>
> > Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
> >'renesas-devel-20160725-v4.7-rc7' tag. We're adding the R8A7792 DU clocks and
> >device nodes. They have been tested on the Blanche board -- I'm not posting the
> >Blanche patch only because it also has some strange interaction with the
> >Ethernet chip, so that NFS root can't work anymore...
>
> Forgot to mention that the patch #2 depends on the R8A7792 DU driver
> patch posted last night.
Thanks.
The driver changes look line an incremental update to what is already done
for other R-Car Gen2 SoCs. And I am assuming that applying these patches
without the driver change is harmless - the driver just won't be
initialised until both the driver and DTS changes are present.
With the above reasoning I have queued up these patches with Geert's
reviewed-by tag. Please let me know if that is not desirable for some
reason.
next prev parent reply other threads:[~2016-08-09 12:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 18:24 [PATCH 0/2] Add R8A7792 DU support Sergei Shtylyov
2016-08-05 18:24 ` Sergei Shtylyov
2016-08-05 18:24 ` Sergei Shtylyov
2016-08-05 18:25 ` [PATCH 1/2] ARM: dts: r8a7792: add DU clocks Sergei Shtylyov
2016-08-05 18:25 ` Sergei Shtylyov
2016-08-05 18:25 ` Sergei Shtylyov
2016-08-08 13:16 ` Geert Uytterhoeven
2016-08-08 13:16 ` Geert Uytterhoeven
2016-08-08 13:16 ` Geert Uytterhoeven
2016-08-05 18:26 ` [PATCH 2/2] ARM: dts: r8a7792: add DU support Sergei Shtylyov
2016-08-05 18:26 ` Sergei Shtylyov
2016-08-08 13:18 ` Geert Uytterhoeven
2016-08-08 13:18 ` Geert Uytterhoeven
2016-08-05 18:28 ` [PATCH 0/2] Add R8A7792 " Sergei Shtylyov
2016-08-05 18:28 ` Sergei Shtylyov
2016-08-09 12:32 ` Simon Horman [this message]
2016-08-09 12:32 ` Simon Horman
2016-08-18 18:00 ` Sergei Shtylyov
2016-08-18 18:00 ` Sergei Shtylyov
2016-08-18 18:00 ` 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=20160809123228.GA5878@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 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.