From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 0/2] Renesas ARM based SoC boards cleanups for v3.12
Date: Sun, 18 Aug 2013 04:03:39 +0000 [thread overview]
Message-ID: <20130818040339.GE30709@verge.net.au> (raw)
In-Reply-To: <20130814081242.GJ30577@quad.lixom.net>
On Wed, Aug 14, 2013 at 01:12:42AM -0700, Olof Johansson wrote:
> On Wed, Aug 07, 2013 at 01:36:37PM +0900, Simon Horman wrote:
> > Hi Olof, Hi Arnd,
> >
> > please consider these Renesas ARM based SoC boards cleanups for v3.12.
> >
> > This pull-request is based on renesas-boards-for-v3.12,
> > which I have previously sent a pull-request for.
> >
> > I have separated these cleanups from those that I included
> > in renesas-cleanup3-for-v3.12 as there are different dependencies
> > involved and this approach seemed simpler somehow.
> >
> >
> > The following changes since commit f79d68da510bf1b95beff4d556b78d06801f11dc:
> >
> > ARM: shmobile: ape6evm: add SDHI interfaces (2013-07-25 14:46:38 +0900)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-boards-cleanup-for-v3.12
>
> Pulled, thanks. FWIW, this could have been baked into boards2.
Thanks. To be honest I am rather unclear on when something should go in a
cleanup branch and when it shouldn't.
prev parent reply other threads:[~2013-08-18 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 4:36 [GIT PULL 0/2] Renesas ARM based SoC boards cleanups for v3.12 Simon Horman
2013-08-07 4:36 ` [GIT PULL 1/2] ARM: shmobile: ape6evm: add "__initconst" annotations where needed Simon Horman
2013-08-07 4:36 ` [GIT PULL 2/2] ARM: shmobile: lager: add missing __initdata Simon Horman
2013-08-14 8:12 ` [GIT PULL 0/2] Renesas ARM based SoC boards cleanups for v3.12 Olof Johansson
2013-08-18 4:03 ` 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=20130818040339.GE30709@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).