linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: kirkwood: convert Guruplug Server Plus to use the device tree
Date: Mon, 7 Jan 2013 19:20:31 +0100	[thread overview]
Message-ID: <20130107182031.GB28008@1wt.eu> (raw)
In-Reply-To: <20130107181731.GQ5075@titan.lakedaemon.net>

On Mon, Jan 07, 2013 at 01:17:31PM -0500, Jason Cooper wrote:
> mach-mvebu is where everything is being migrated to once the DT
> conversion is complete.  We use the name internally to refer to any SoCs
> created by Marvell in the EBU division.
> 
> So, yes, it's kirkwood, but it falls under mvebu stuff.  Just like dove
> and orion5x.

OK, that was not obvious to me, since till now for me mvebu was only
the new armada370/XP boards. But that makes sense and it will certainly
make code sharing easier !

Thanks for your explanation!

Willy

      reply	other threads:[~2013-01-07 18:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02 15:51 [PATCH] ARM: kirkwood: convert Guruplug to use the device tree Willy Tarreau
2012-12-02 23:09 ` Jason Cooper
2012-12-02 23:22   ` Willy Tarreau
2012-12-02 23:41     ` Jason Cooper
2012-12-02 23:48       ` Willy Tarreau
2012-12-03  0:09         ` Jason Cooper
2012-12-09 18:40       ` [PATCH v2] ARM: kirkwood: convert Guruplug Server Plus " Willy Tarreau
2012-12-09 22:02         ` Jason Cooper
2012-12-09 22:37           ` Willy Tarreau
2012-12-09 23:57             ` Jason Cooper
2013-01-07 17:48         ` Jason Cooper
2013-01-07 18:08           ` Willy Tarreau
2013-01-07 18:17             ` Jason Cooper
2013-01-07 18:20               ` Willy Tarreau [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=20130107182031.GB28008@1wt.eu \
    --to=w@1wt.eu \
    --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).