From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] ARM: mvebu: soc for v3.10
Date: Sun, 17 Mar 2013 23:26:10 +0100 [thread overview]
Message-ID: <51464302.5000906@free-electrons.com> (raw)
In-Reply-To: <1363551341.10D8ED563.32562@triton>
Hi Jason,
On 03/17/2013 09:15 PM, Jason Cooper wrote:
> The following changes since commit 207b6b8da3195dafe3e0d2143262640ddace74af:
>
> Merge branch 'mvebu/drivers' into mvebu/soc
>
> are available in the git repository at:
>
> git://git.infradead.org/users/jcooper/linux.git tags/soc_changes_for_v3.10
>
> for you to fetch changes up to c135394ade12b00be1fdd04f68ff8470207a9b32:
>
> arm: plat-orion: remove addr-map code
>
> ----------------------------------------------------------------
> mvebu soc changes for v3.10
>
> - use mvebu-mbus driver for:
> - kirkwood
> - dove
> - orion5x
> - mv78xx
> - mvebu
>
> - depends
> - tags/cleanup_for_v3.10 (mvebu/cleanup)
> - tags/drivers_for_v3.10 (mvebu/drivers)
> ----------------------------------------------------------------
> Thomas Petazzoni (6):
> arm: mach-mvebu: convert to use mvebu-mbus driver
> arm: mach-kirkwood: convert to use mvebu-mbus driver
> arm: mach-dove: convert to use mvebu-mbus driver
> arm: mach-orion5x: convert to use mvebu-mbus driver
> arm: mach-mv78xx0: convert to use the mvebu-mbus driver
Could you hold on this one?
I managed to test Thomas patch set for a mv78x00 based board on Friday,
and I found a small bug. Thomas has a fix for it and he plans to send
a V3 with this fix next week.
Thanks,
Gregory
next prev parent reply other threads:[~2013-03-17 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 20:15 [GIT PULL 0/3] ARM: mvebu: changes for v3.10 Jason Cooper
2013-03-17 20:15 ` [GIT PULL 1/3] ARM: mvebu: cleanup " Jason Cooper
2013-03-18 14:50 ` Arnd Bergmann
2013-03-17 20:15 ` [GIT PULL 2/3] ARM: mvebu: drivers " Jason Cooper
2013-03-17 20:15 ` [GIT PULL 3/3] ARM: mvebu: soc " Jason Cooper
2013-03-17 22:26 ` Gregory CLEMENT [this message]
2013-03-18 1:07 ` Jason Cooper
2013-03-18 16:18 ` Thomas Petazzoni
2013-03-18 20:50 ` Arnd Bergmann
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=51464302.5000906@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--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;
as well as URLs for NNTP newsgroup(s).