From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM-based platforms updates for v3.5
Date: Sat, 12 May 2012 20:17:14 +0000 [thread overview]
Message-ID: <201205122217.14650.rjw@sisk.pl> (raw)
In-Reply-To: <201205122158.13999.rjw@sisk.pl>
On Saturday, May 12, 2012, Rafael J. Wysocki wrote:
> On Saturday, May 12, 2012, Olof Johansson wrote:
> > On Fri, May 11, 2012 at 12:01 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > > Hi,
> > >
> > > Please pull changes since commit d48b97b403d23f6df0b990cee652bdf9a52337a3
> > >
> > > Linux 3.4-rc6
> > >
> > > with top-most commit 5658c94096c16e769203b6dea5e5f04e7ff12633
> > >
> > > Merge branch 'renesas-kzm9g' into renesas-soc-new
> > >
> > > from the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/renesas.git soc-new
> > >
> > > to receive new Renesas ARM-based platforms material for v3.5. Included are:
> > >
> > > * Urgent regression and SMP fixes (also included in the fixes branch that I've
> > > just sent a separate pull request for in the hope it is still possible to
> > > push them for v3.4). Two of those fixes are duplicated in the renesas-sh7372
> > > branch, which is because I learned that they were fixes for recent
> > > regressions after they had gone to that branch. Sorry about that.
> > >
> > > * Updates for boards based on the sh7372 and r8a7740 SoCs.
> > >
> > > * Support for 2 new boards, armadillo800eva and KZM-A9-GT.
> >
> > Hi Rafael,
> >
> > If you take a look at how the other ARM subarch maintainers organize
> > the patches that they feed up to us, you'll see that they group them
> > either per functional topic, or more commonly per subject such as
> > "core soc updates", "soc driver updates", "board updates", "device
> > tree updates", "cleanup", and so on.
> >
> > That fits the model we've been having on arm-soc as well, since we
> > split our tree up per category like that, and send those cross-section
> > branches between different vendors (but same categories) up to Linus
> > that way.
> >
> >
> > So, would you mind taking a look at what you have in the new-soc
> > branch and reshuffling things a bit? Looking at the history of the
> > new-soc branch and the rest of the repo, it seems that you're already
> > more or less organizing your tree the way I am asking for, it's just
> > that you merged them all together before sending this pull request.
>
> Well.
>
> I'd prefer not to rebase any branches and move commits around if that's
> what you're talking about, because I have a rule that my branches are not
> rebased, except for the next one.
I will have to rebase the whole thing anyway because of the changes in
"fixes", so I think I'll just create new branches and send pull requests
again.
Thanks,
Rafael
next prev parent reply other threads:[~2012-05-12 20:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 18:59 [GIT PULL] Renesas ARM-based platforms updates for v3.5 Rafael J. Wysocki
2012-05-12 5:29 ` Olof Johansson
2012-05-12 19:58 ` Rafael J. Wysocki
2012-05-12 20:17 ` Rafael J. Wysocki [this message]
2012-05-12 23:04 ` Olof Johansson
2012-05-12 21:07 ` [GIT PULL] Renesas ARM-based platforms: core SoC " Rafael J. Wysocki
2012-05-12 21:18 ` [GIT PULL] Renesas ARM-based platforms: board support " Rafael J. Wysocki
2012-05-13 4:24 ` Olof Johansson
2012-05-12 21:23 ` [GIT PULL] Renesas ARM-based platforms: new boards support " Rafael J. Wysocki
2012-05-13 6:29 ` Olof Johansson
2012-05-14 7:13 ` Magnus Damm
2012-05-15 19:58 ` Arnd Bergmann
2012-05-16 6:17 ` Olof Johansson
2012-05-14 21:43 ` [GIT PULL][Update] " Rafael J. Wysocki
2012-05-15 8:40 ` Arnd Bergmann
2012-05-15 15:30 ` Arnd Bergmann
2012-05-15 15:49 ` Rafael J. Wysocki
2012-05-15 20:03 ` Arnd Bergmann
2012-05-15 15:50 ` Rafael J. Wysocki
2012-05-12 23:29 ` [GIT PULL] Renesas ARM-based platforms: core SoC updates " Olof Johansson
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=201205122217.14650.rjw@sisk.pl \
--to=rjw@sisk.pl \
--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).