From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 00/13] Core support for Marvell Armada 375 and 38x
Date: Thu, 20 Feb 2014 10:46:44 +0100 [thread overview]
Message-ID: <20140220104644.318ac3f7@skate> (raw)
In-Reply-To: <20140217232035.GH7862@titan.lakedaemon.net>
Dear Jason Cooper,
On Mon, 17 Feb 2014 18:20:35 -0500, Jason Cooper wrote:
> Whole series applied as follows:
>
> Patches 1-6, 9, 13 -> mvebu/soc-3xx
>
> Patches 7, 8, 10, 11 -> mvebu/dt-3xx
I might be missing something, but while I see the soc-3xx branch, I
don't see the dt-3xx branch in the mvebu repo. Did you forget to push
this branch, maybe?
However, I do see that you have merged dt-3xx in mvebu/for-next, so it
looks like the branch exists somewhere.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-20 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 14:23 [PATCH v4 00/13] Core support for Marvell Armada 375 and 38x Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 01/13] ARM: mvebu: rename armada-370-xp.c to board-v7.c Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 02/13] ARM: mvebu: rename DT machine structure for Armada 370/XP Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 03/13] ARM: mvebu: make CPU_PJ4B selection a per-SoC choice Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 04/13] ARM: mvebu: add Armada 375 support to the system-controller driver Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 05/13] ARM: mvebu: add initial support for the Armada 375 SOCs Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 06/13] ARM: mvebu: add workaround for data abort issue on Armada 375 Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 07/13] ARM: mvebu: add Device Tree description of the Armada 375 SoC Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 08/13] ARM: mvebu: add Device Tree for the Armada 375 DB board Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 09/13] ARM: mvebu: add initial support for the Armada 380/385 SOCs Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 10/13] ARM: mvebu: add Device Tree description of the Armada 380/385 SoCs Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 11/13] ARM: mvebu: add Device Tree for the Armada 385 DB board Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 12/13] ARM: mvebu: update defconfigs for Armada 375 and 38x Thomas Petazzoni
2014-02-17 14:23 ` [PATCH v4 13/13] Documentation: arm: update Marvell documentation about Armada 375/38x Thomas Petazzoni
2014-02-17 23:20 ` [PATCH v4 00/13] Core support for Marvell Armada 375 and 38x Jason Cooper
2014-02-18 8:33 ` Thomas Petazzoni
2014-02-20 9:46 ` Thomas Petazzoni [this message]
2014-02-20 23:41 ` Jason Cooper
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=20140220104644.318ac3f7@skate \
--to=thomas.petazzoni@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).