From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 00/12] Second Round of Renesas ARM Based SoC Updates for v3.15
Date: Sat, 22 Feb 2014 10:41:32 +0900 [thread overview]
Message-ID: <20140222014132.GA5393@verge.net.au> (raw)
In-Reply-To: <20140221222544.GA13233@quad.lixom.net>
On Fri, Feb 21, 2014 at 02:25:44PM -0800, Olof Johansson wrote:
> On Thu, Feb 20, 2014 at 01:43:24AM -0800, Olof Johansson wrote:
> > On Thu, Feb 13, 2014 at 05:04:56PM +0900, Simon Horman wrote:
> > > Hi Olof, Hi Kevin, Hi Arnd,
> > >
> > > please consider this second round of Renesas ARM Based SoC updates for v3.15.
> > >
> > > This pull-request is based on the first round of such changes,
> > > tagged as renesas-soc-for-v3.15, which I have previously sent a
> > > pull-request for.
> > >
> > >
> > > The following changes since commit 012a7069b5a10a0851584d71a1facdc40a972319:
> > >
> > > ARM: shmobile: r8a7790: Add PCI USB host clock support (2014-02-04 10:25:03 +0900)
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc2-for-v3.15
> >
> > Hi,
> >
> > I'm stopping my merges for the night here, so I haven't merged this but I'll
> > likely do it tomorrow. I did have comments on one of the patches though (that
> > adds a new include/mach file that's not really needed). Fixing that can be done
> > incrementally though, especially if you have downstream users of this branch.
>
> Simon,
>
> I think it'd fit our workflow better if you kept all the clock changes in
> a topic branch this release, instead of mingling them with the SoC code.
> There is enough of them that it's not just a silly short branch, and there's
> little overlap with the rest of the soc code changes you have (i.e. it makes
> more sense for us to merge in with a drivers branch instead of keeping it all
> with soc).
>
> Would you mind respinning and sorting that out to a separate topic? Since
> I've already merged the first soc branch (but treated it like a clock
> branch), feel free to keep that as a base for the new clock branch
> (but not for the new soc branch, ideally).
Sure, I will see about doing that.
In the mean time, please disregard "Third Round of Renesas ARM Based SoC
Updates", which I sent before I saw this email.
I think that all the other pull-request that I sent yesterday
should be unaffected by this change.
prev parent reply other threads:[~2014-02-22 1:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 8:04 [GIT PULL 00/12] Second Round of Renesas ARM Based SoC Updates for v3.15 Simon Horman
2014-02-13 8:13 ` [PATCH 01/12] ARM: shmobile: Use 64-bit dma_addr_t on r8a7790/r8a7791 Simon Horman
2014-02-13 8:13 ` [PATCH 02/12] ARM: shmobile: Break out R-Car SYSC PM code Simon Horman
2014-02-13 8:13 ` [PATCH 03/12] ARM: shmobile: r8a7790 SYSC setup code Simon Horman
2014-02-13 8:13 ` [PATCH 04/12] ARM: shmobile: r8a7790 CA7-SCU enablement Simon Horman
2014-02-13 8:13 ` [PATCH 05/12] ARM: shmobile: r8a7790 CA15-SCU enablement Simon Horman
2014-02-13 8:13 ` [PATCH 06/12] ARM: shmobile: r8a7778: add audio clock in new style Simon Horman
2014-02-13 8:13 ` [PATCH 07/12] ARM: shmobile: r8a7790: add audio clock Simon Horman
2014-02-13 8:13 ` [PATCH 08/12] ARM: shmobile: r7s72100 clock: Add RSPI clocks Simon Horman
2014-02-13 8:13 ` [PATCH 09/12] ARM: shmobile: r7s72100 clock: Add RSPI clocks for DT Simon Horman
2014-02-13 8:13 ` [PATCH 10/12] ARM: shmobile: r8a7791 clock: add QSPI clocks Simon Horman
2014-02-13 8:14 ` [PATCH 11/12] ARM: shmobile: r7s72100: Add clock for r7s72100-ether Simon Horman
2014-02-13 8:14 ` [PATCH 12/12] ARM: shmobile: r8a7790: Correct SYS DMAC clock defines Simon Horman
2014-02-20 9:43 ` [GIT PULL 00/12] Second Round of Renesas ARM Based SoC Updates for v3.15 Olof Johansson
2014-02-20 23:27 ` Simon Horman
2014-02-21 22:25 ` Olof Johansson
2014-02-22 1:41 ` 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=20140222014132.GA5393@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).