From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Mike Turquette <mturquette@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH v2 1/5] ARM: shmobile: r8a7740: document MSTP clock support
Date: Sat, 23 Aug 2014 20:11:52 +0900 [thread overview]
Message-ID: <20140823111151.GA27759@verge.net.au> (raw)
In-Reply-To: <20140822084657.GF18670@verge.net.au>
On Fri, Aug 22, 2014 at 05:46:58PM +0900, Simon Horman wrote:
> On Fri, Aug 22, 2014 at 09:44:09AM +0200, Geert Uytterhoeven wrote:
> > Hi Simon,
> >
> > On Fri, Aug 22, 2014 at 3:04 AM, Simon Horman <horms@verge.net.au> wrote:
> > > On Mon, Aug 11, 2014 at 10:12:14AM +0900, Simon Horman wrote:
> > >> On Fri, Aug 08, 2014 at 04:23:08PM +0200, Ulrich Hecht wrote:
> > >> > Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> > >>
> > >> Acked-by: Simon Horman <horms+renesas@verge.net.au>
> > >>
> > >> Mike, could you consider taking this?
> > >
> > > Hi Mike,
> > >
> > > I'm wondering if you could take moment to consider this patch.
> > > It is a dependency for enabling ccf and in turn multiplatform on
> > > the r8a7740 SoC.
> >
> > Sidenote: as this patch only updates the documentation, and the driver
> > won't use the newly added value (for now), there's no hard dependency.
> > Furthermore, adding this value is done following the spirit of the existing
> > values, and thus I think you can just continue going forward with the parts
> > that fall under the shmobile jurisdiction.
>
> Hi Geert,
>
> I had a conversation with Magnus earlier today and I believe that
> all three of us are (now) in agreement on the point you have made above.
>
> I'd like to allow myself the weekend to think about this and
> if no issues have surfaced by then I plan to take the remaining
> patches of this series into the next branch of the renesas tree.
I have now queued up patches 2 - 5.
next prev parent reply other threads:[~2014-08-23 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 14:23 [PATCH v2 0/5] ARM: shmobile: r8a7740: add clocks to DT Ulrich Hecht
2014-08-08 14:23 ` [PATCH v2 1/5] ARM: shmobile: r8a7740: document MSTP clock support Ulrich Hecht
2014-08-11 1:12 ` Simon Horman
2014-08-14 22:37 ` Simon Horman
2014-08-22 1:04 ` Simon Horman
2014-08-22 7:44 ` Geert Uytterhoeven
2014-08-22 8:46 ` Simon Horman
2014-08-23 11:11 ` Simon Horman [this message]
2014-08-08 14:23 ` [PATCH v2 2/5] ARM: shmobile: r8a7740: clock register bits Ulrich Hecht
2014-08-22 2:49 ` Simon Horman
2014-08-08 14:23 ` [PATCH v2 3/5] ARM: shmobile: r8a7740: add SoC clocks to DTS Ulrich Hecht
2014-08-08 14:23 ` [PATCH v2 4/5] ARM: shmobile: r8a7740: add MSTP clock assignments to DT Ulrich Hecht
2014-08-08 14:23 ` [PATCH v2 5/5] ARM: shmobile: armadillo800eva-reference: add clock overrides to DTS Ulrich Hecht
2014-08-19 6:48 ` [PATCH v2 0/5] ARM: shmobile: r8a7740: add clocks to DT Magnus Damm
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=20140823111151.GA27759@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@linaro.org \
--cc=ulrich.hecht+renesas@gmail.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).