From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL V2] ARM: mvebu: SoC changes for v3.17
Date: Mon, 7 Jul 2014 22:28:47 -0700 [thread overview]
Message-ID: <20140708052847.GF28931@quad.lixom.net> (raw)
In-Reply-To: <20140701121119.GD23978@titan.lakedaemon.net>
On Tue, Jul 01, 2014 at 08:11:19AM -0400, Jason Cooper wrote:
> Guys,
>
> Here's most of the SoC changes for mvebu so far. It's looking to be a
> slow cycle for us this time around (famous last words ;-) ).
>
> The only unusual item here is the setup file for the kirkwood netxbig
> board. Andrew is working on a DT binding for the LEDs, but it is
> non-trivial. By accepting this now, we can delete mach-kirkwood/, which
> is a good thing. :) I hope to see patches from Andrew on this soon.
>
> As usual, based on v3.16-rc1, no dependencies, been in -next several
> days.
>
> Changes for V2: move three patches out of mvebu/soc and into mvebu/fixes
> for inclusion in v3.16.
>
> Please pull.
>
> thx,
>
> Jason.
>
> The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
>
> Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
>
> are available in the git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-soc-3.17
Merged.
-Olof
prev parent reply other threads:[~2014-07-08 5:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 12:46 [GIT PULL] ARM: mvebu: SoC changes for v3.17 Jason Cooper
2014-06-28 14:23 ` Thomas Petazzoni
2014-06-28 15:07 ` Jason Cooper
2014-06-28 15:20 ` Thomas Petazzoni
2014-06-29 9:35 ` Russell King - ARM Linux
2014-06-29 9:56 ` Thomas Petazzoni
2014-06-30 10:22 ` Thomas Petazzoni
2014-06-30 10:29 ` Russell King - ARM Linux
2014-06-30 12:06 ` Jason Cooper
2014-06-30 12:11 ` Thomas Petazzoni
2014-06-30 12:14 ` Jason Cooper
2014-06-30 17:44 ` Jason Cooper
2014-06-30 18:50 ` Thomas Petazzoni
2014-07-01 12:11 ` [GIT PULL V2] " Jason Cooper
2014-07-08 5:28 ` Olof Johansson [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=20140708052847.GF28931@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox