From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC CPG MSTP Clock Domain Updates for v4.3
Date: Thu, 13 Aug 2015 11:30:21 +0200 [thread overview]
Message-ID: <20150813093021.GG30160@localhost> (raw)
In-Reply-To: <20150812084822.GB16058@verge.net.au>
On Wed, Aug 12, 2015 at 05:48:22PM +0900, Simon Horman wrote:
> On Tue, Aug 11, 2015 at 03:38:43PM +0200, Olof Johansson wrote:
> > On Fri, Aug 07, 2015 at 11:12:03AM +0900, Simon Horman wrote:
> > > Hi Olof, Hi Kevin, Hi Arnd,
> > >
> > > Please consider these Renesas ARM based SoC CPG MSTP clock domain updates
> > > for v4.3.
> > >
> > > This pull request is based on "Third Round of Renesas ARM Based SoC DT
> > > Updates for v4.3", tagged as renesas-dt3-for-v4.3, which I have also sent a
> > > pull-request for.
> > >
> > > The reason for that base is that the DT changes in this series update nodes
> > > added in that tag.
> > >
> > > This series begins with driver changes and follows up with DT changes.
> > > The latter depend on the former.
> >
> > I see the acked-by tags on the clk patches, but it took some searching to find
> > the ack email from Stephen.
> >
> > Can you please make our homework a bit easier when providing that in
> > the future?
>
> Sure, I hadn't realised that you liked to track down Acks to that extent.
>
> As practice for myself I've included some notes in the repost of the
> patches in question. Please let me know if you need something different.
It's one of those things that we check in on every now and then, just to make
sure that there weren't comments from the other maintainer that were missed.
We're more likely to do it on pull requests that didn't have the other
maintainer on Cc, FWIW. :)
-Olof
next prev parent reply other threads:[~2015-08-13 9:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 2:12 [GIT PULL] Renesas ARM Based SoC CPG MSTP Clock Domain Updates for v4.3 Simon Horman
2015-08-07 2:12 ` [PATCH 01/12] clk: shmobile: Add CPG/MSTP Clock Domain support Simon Horman
2015-08-07 2:12 ` [PATCH 02/12] clk: shmobile: r8a7778: " Simon Horman
2015-08-07 2:12 ` [PATCH 03/12] clk: shmobile: r8a7779: " Simon Horman
2015-08-07 2:12 ` [PATCH 04/12] clk: shmobile: rcar-gen2: " Simon Horman
2015-08-07 2:12 ` [PATCH 05/12] clk: shmobile: rz: " Simon Horman
2015-08-07 2:12 ` [PATCH 06/12] ARM: shmobile: r7s72100 dtsi: Add CPG/MSTP Clock Domain Simon Horman
2015-08-07 2:12 ` [PATCH 07/12] ARM: shmobile: r8a7778 " Simon Horman
2015-08-07 2:12 ` [PATCH 08/12] ARM: shmobile: r8a7779 " Simon Horman
2015-08-07 2:12 ` [PATCH 09/12] ARM: shmobile: r8a7790 " Simon Horman
2015-08-07 2:12 ` [PATCH 10/12] ARM: shmobile: r8a7791 " Simon Horman
2015-08-07 2:12 ` [PATCH 11/12] ARM: shmobile: r8a7793 " Simon Horman
2015-08-07 2:12 ` [PATCH 12/12] ARM: shmobile: r8a7794 " Simon Horman
2015-08-11 13:38 ` [GIT PULL] Renesas ARM Based SoC CPG MSTP Clock Domain Updates for v4.3 Olof Johansson
2015-08-12 8:48 ` Simon Horman
2015-08-13 9:30 ` Olof Johansson [this message]
2015-08-11 13:42 ` Olof Johansson
2015-08-12 8:46 ` 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=20150813093021.GG30160@localhost \
--to=olof@lixom.net \
--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).