From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL]
Date: Sun, 01 Jul 2012 17:40:44 +0200 [thread overview]
Message-ID: <4FF06F7C.8050701@antcom.de> (raw)
In-Reply-To: <CAOesGMhbRnU3wExk88Wkc2=YwbuNpt_uPEsAfmZh6_os9CkqiA@mail.gmail.com>
Hi,
On 01/07/12 01:29, Olof Johansson wrote:
>> This time, purely mach-lpc32xx specific patches.
>>
>> Please tell if sth. is missing, so I can know if I can build upon that. (I'm
>> already collecting new patches on top of this branch.)
>
> I'm very sorry for the slow response to this pull request.
>
> The contents of it in itself looks good, but given the amount of
> patches that you are building up now, I think it's time to start
> organizing into topic branches that fit the structure of arm-soc a bit
> better.
>
> In other words, it makes sense to separate out things such as dts
> updates in their own branch, core SoC updates in one, etc.
>
> Given that you've based other work on top of this combined branch now,
> and the fact that I should have gotten back to you sooner about it,
> I'm going to pull it in under our next/soc branch this time. But I'd
> like to see more topic-oriented pull requests in the future, ideally
> for your updates here but definitely in the branches you stage for
> 3.7.
I'm fine with this.
Building upon the branch you just pulled, I'll separate out the further
patches into topic branches. Is there a certain set of those which I
should use to adjust to arm-soc structure? E.g.:
lpc32xx/core
lpc32xx/defconfig
lpc32xx/dts
?
Thanks for pointing this out!
Roland
next prev parent reply other threads:[~2012-07-01 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 20:48 [GIT PULL] Roland Stigge
2012-06-30 23:29 ` Olof Johansson
2012-07-01 15:40 ` Roland Stigge [this message]
2012-07-02 16:25 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2019-02-11 20:48 Kevin Hilman
2019-02-11 20:56 ` Kevin Hilman
2011-12-19 11:29 Sascha Hauer
2011-12-20 5:33 ` Olof Johansson
2010-09-10 12:52 Nicolas Ferre
2010-09-10 13:16 ` Jean-Christophe PLAGNIOL-VILLARD
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=4FF06F7C.8050701@antcom.de \
--to=stigge@antcom.de \
--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).