From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/6] ARM: SoC changes for 3.14
Date: Thu, 23 Jan 2014 10:36:22 -0800 [thread overview]
Message-ID: <1390502188-16896-1-git-send-email-olof@lixom.net> (raw)
Here are the main branches for arm-soc for the 3.14 merge window. We'll have a
few more patches towards the end, but this is the bulk of it.
Nothing too surprising in any of it, and we've been able to stay away
from too much conflicts this release cycle, I think the total was around
3 and none of them are messy (proposed resolution in each pull request)
I've pushed up a "resolved-for-linus" branch in case you want to compare
resolutions.
Please pull. Thanks!
-Olof
next reply other threads:[~2014-01-23 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 18:36 Olof Johansson [this message]
2014-01-23 18:36 ` [GIT PULL 1/6] ARM: SoC non-critical fixes for 3.14 Olof Johansson
2014-01-23 18:36 ` [GIT PULL 2/6] ARM: SoC cleanups " Olof Johansson
2014-01-23 18:36 ` [GIT PULL 3/6] ARM: SoC platform changes " Olof Johansson
2014-01-23 18:36 ` [GIT PULL 4/6] ARM: SoC DT updates " Olof Johansson
2014-01-23 18:36 ` [GIT PULL 5/6] ARM: SoC board " Olof Johansson
2014-01-23 18:36 ` [GIT PULL 6/6] ARM: driver " 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=1390502188-16896-1-git-send-email-olof@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox