Thread (4 messages) 4 messages, 2 authors, 2012-07-02
  • [GIT PULL] · Roland Stigge <hidden> · 2012-06-18
  • [GIT PULL] · Olof Johansson <hidden> · 2012-06-30
  • [GIT PULL] · Roland Stigge <hidden> · 2012-07-01
  • [GIT PULL] · Olof Johansson <hidden> · 2012-07-02

[GIT PULL]

From: Roland Stigge <hidden>
Date: 2012-07-01 15:40:44

Hi,

On 01/07/12 01:29, Olof Johansson wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help