Linux-ARM-Kernel Archive on
 help / color / Atom feed
From: (Olof Johansson)
Subject: [GIT PULL]
Date: Sat, 30 Jun 2012 16:29:27 -0700
Message-ID: <> (raw)
In-Reply-To: <>


On Mon, Jun 18, 2012 at 1:48 PM, Roland Stigge <> wrote:
> Hi Arnd and Olof,
> this is the pull request for the 22 patches we discussed last week, still same
> commits in the same branch (the 23rd patch was removed from the series, as
> discussed on the list).
> 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

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

Let me know if you have any questions, or if there's something we
should explain a bit better about how we organize the branches.

> git:// lpc32xx-next

Pulled as lpc32xx/devel and merged into next/soc. You can still use
this branch as a base for more fine-grained topic branches, we should
be able to deal with those dependencies in arm-soc.



  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 20:48 stigge
2012-06-30 23:29 ` olof [this message]
2012-07-01 15:40   ` stigge
2012-07-02 16:25     ` olof
  -- 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 s.hauer
2011-12-20  5:33 ` olof
2010-09-10 12:52 nicolas.ferre
2010-09-10 13:16 ` plagnioj

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-ARM-Kernel Archive on

Archives are clonable:
	git clone --mirror linux-arm-kernel/git/0.git
	git clone --mirror linux-arm-kernel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-arm-kernel linux-arm-kernel/ \
	public-inbox-index linux-arm-kernel

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox