From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: mvebu: soc changes for v3.15 (incr. pull #2)
Date: Mon, 17 Mar 2014 10:53:18 +0100 [thread overview]
Message-ID: <201403171053.18567.arnd@arndb.de> (raw)
In-Reply-To: <20140301041947.GR1872@titan.lakedaemon.net>
On Saturday 01 March 2014, Jason Cooper wrote:
> All,
>
> This is a big one for us :) You've already pulled part of this as
> mvebu/soc-3xx. I merged that branch and mvebu/soc-kw back into
> mvebu/soc. This whole lot has been in -next all week. Two minor issues
> were discovered and patches added to correct them.
>
> At this point I think the kirkwood and armada changes have been shaken
> out enough that they no longer need their own branches. If you don't
> agree, just let me know and I'll send separate pull requests for the
> per-SoC branches.
>
> This is an incremental pull request from tags/mvebu-soc-3.15 in the
> mvebu/soc branch up to tags/mvebu-soc-3.15-2.
>
> There will be a small conflict between this branch and mvebu/dt. This
> is due to the kirkwood migration and maintaining bisectability. I'll
> detail the conflict in the mvebu/dt pull request.
>
> Please pull.
>
Pulled into next/soc, sorry for the delay.
I noticed that the shortlog in the pull request listed the parts
from mvebu/soc-3xx again, which confused me a bit because they
didn't show up in the merge, but I checked that it's all good.
Arnd
prev parent reply other threads:[~2014-03-17 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 4:19 [GIT PULL] ARM: mvebu: soc changes for v3.15 (incr. pull #2) Jason Cooper
2014-03-17 9:53 ` Arnd Bergmann [this message]
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=201403171053.18567.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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