From: Simon Horman <horms@verge.net.au>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: r8a7792: add IMR-L[S]X3 clocks
Date: Fri, 30 Jun 2017 11:47:57 +0200 [thread overview]
Message-ID: <20170630094757.GC26710@verge.net.au> (raw)
In-Reply-To: <fbd0e4c2-746c-8f74-a8e5-ab971a087aed@cogentembedded.com>
On Wed, Jun 28, 2017 at 11:49:01PM +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 03/29/2017 11:04 AM, Simon Horman wrote:
>
> >>>Still not cover letter but I think it's better now, so I won't retry...
> >>>The patches are against Simon Horman's 'renesas.git' repo,
> >>>'renesas-devel-20170321-v4.11-rc3' tag.
> >>
> >> The patches depend on the IMR driver patches adding the IMR-L[S]X3
> >>support for the "compatible" values.
> >
> >I have marked these patches as deferred accordingly.
>
> Actually, the 1st patch in htis series doesn't depend on anything and
> should still apply (with offsets).
I'd prefer to take both patches at the same time unless there is a strong
motivation to just take the first one.
next prev parent reply other threads:[~2017-06-30 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 20:04 [PATCH 1/2] ARM: dts: r8a7792: add IMR-L[S]X3 clocks Sergei Shtylyov
2017-03-21 20:08 ` Sergei Shtylyov
2017-03-21 20:14 ` Sergei Shtylyov
2017-03-29 8:04 ` Simon Horman
2017-06-28 20:49 ` Sergei Shtylyov
2017-06-30 9:47 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
1970-01-01 0:00 Sergei Shtylyov
2017-03-21 20:00 ` Sergei Shtylyov
2017-03-22 9:31 ` Geert Uytterhoeven
2017-06-30 10:01 ` Simon Horman
2017-06-30 10:47 ` 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=20170630094757.GC26710@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@armlinux.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