From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/3] ARM: arm-soc: Third and final batch foe 3.8
Date: Fri, 14 Dec 2012 14:04:41 -0800 [thread overview]
Message-ID: <20121214220441.GA11363@quad.lixom.net> (raw)
Hi Linus,
Here is the last batch of branches for 3.8. It's wrapping up merges for
SPEAr and socfpga, some additional contents for Exynos and shmobile and
a large update for mvebu/kirkwood.
For kirkwood, we're working on figuring out the workflow better with the
submaintainers, they have a rapid pace of development and end up with a
lot of interdependent topic branches. So we grouped them in a topic on
their own this merge window; something we're trying to avoid overall.
Same procedure as last time, merge conflicts documented in each request
and *-resolved branches pushed for reference.
And thanks for your tolerance of merge conflicts in this merge window,
it's been a relatively bad one and we'll work to avoid more of the silly
ones for 3.9.
>From here on out it'll mostly be fixes, and possibly a few straggling
patches.
Thanks,
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: torvalds@linux-foundation.org
Cc: olof@lixom.net, arm@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL 0/3] ARM: arm-soc: Third and final batch foe 3.8
Date: Fri, 14 Dec 2012 14:04:41 -0800 [thread overview]
Message-ID: <20121214220441.GA11363@quad.lixom.net> (raw)
Hi Linus,
Here is the last batch of branches for 3.8. It's wrapping up merges for
SPEAr and socfpga, some additional contents for Exynos and shmobile and
a large update for mvebu/kirkwood.
For kirkwood, we're working on figuring out the workflow better with the
submaintainers, they have a rapid pace of development and end up with a
lot of interdependent topic branches. So we grouped them in a topic on
their own this merge window; something we're trying to avoid overall.
Same procedure as last time, merge conflicts documented in each request
and *-resolved branches pushed for reference.
And thanks for your tolerance of merge conflicts in this merge window,
it's been a relatively bad one and we'll work to avoid more of the silly
ones for 3.9.
>From here on out it'll mostly be fixes, and possibly a few straggling
patches.
Thanks,
-Olof
next reply other threads:[~2012-12-14 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 22:04 Olof Johansson [this message]
2012-12-14 22:04 ` [GIT PULL 0/3] ARM: arm-soc: Third and final batch foe 3.8 Olof Johansson
2012-12-14 22:05 ` [GIT PULL 1/3] ARM: arm-soc: SoC updates, take 2 Olof Johansson
2012-12-14 22:05 ` Olof Johansson
2012-12-14 22:06 ` [GIT PULL 2/3] ARM: arm-soc: Device-tree " Olof Johansson
2012-12-14 22:06 ` Olof Johansson
2012-12-14 22:06 ` [GIT PULL 3/3] ARM: arm-soc: Updates for Marvell mvebu/kirkwood Olof Johansson
2012-12-14 22:06 ` 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=20121214220441.GA11363@quad.lixom.net \
--to=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.