From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/5] Third round of Renesas ARM-based SoC board updates for v3.12
Date: Fri, 30 Aug 2013 09:19:29 +0900 [thread overview]
Message-ID: <20130830001929.GG25167@verge.net.au> (raw)
In-Reply-To: <20130829235958.GI29606@quad.lixom.net>
On Thu, Aug 29, 2013 at 04:59:58PM -0700, Olof Johansson wrote:
> Hi Simon,
>
> On Wed, Aug 28, 2013 at 10:37:40AM +0900, Simon Horman wrote:
> > please consider this third round of Renesas ARM based SoC board
> > updates for v3.12.
>
> It's time to start closing down the tree, so please hold these (and the other
> branches you sent pull requests for on the 28th) for right after -rc1. We'll of
> course be happy to take fixes to things before then, but cleanups and new code
> should wait.
>
> That will also simplify a lot of the dependencies on these late branches. :)
Understood. I'll hold these requests off for the next cycle and
only send fixes for the rest of this cycle.
prev parent reply other threads:[~2013-08-30 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 1:37 [GIT PULL 0/5] Third round of Renesas ARM-based SoC board updates for v3.12 Simon Horman
2013-08-28 1:37 ` [PATCH 1/5] ARM: shmobile: marzen: Add Display Unit support Simon Horman
2013-08-28 1:37 ` [PATCH 2/5] ARM: shmobile: lager: Constify platform data and resources Simon Horman
2013-08-28 1:37 ` [PATCH 3/5] ARM: shmobile: lager: Add Display Unit support Simon Horman
2013-08-28 1:37 ` [PATCH 4/5] ARM: shmobile: ape6evm: update MMC0, SDHI0 and SDHI1 with correct regulators Simon Horman
2013-08-28 1:37 ` [PATCH 5/5] ARM: shmobile: lager: Fix Display Unit platform data Simon Horman
2013-08-28 1:44 ` [GIT PULL 0/5] Third round of Renesas ARM-based SoC board updates for v3.12 Simon Horman
2013-08-29 23:59 ` Olof Johansson
2013-08-30 0:19 ` 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=20130830001929.GG25167@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