From: Andrew Lunn <andrew@lunn•ch>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons•com>
Cc: Jason Cooper <jason@lakedaemon•net>,
"David S. Miller" <davem@davemloft•net>,
netdev@vger•kernel.org,
Gregory Clement <gregory.clement@free-electrons•com>,
Andrew Lunn <andrew@lunn•ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail•com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons•com>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] net: ethernet: remove unneeded dependency of mvneta and update help text
Date: Tue, 18 Feb 2014 14:58:09 +0100 [thread overview]
Message-ID: <20140218135809.GD17984@lunn.ch> (raw)
In-Reply-To: <20140218141303.77c77272@skate>
> At this point, I don't expect to see this IP in any other SOCs than
> Marvell Armada EBU, so I'll resend with a "depends on PLAT_ORION", as I
> agree it is much safer in terms of build problems.
Hi Thomas
PLAT_ORION is a bit of an odd thing now.
For me, PLAT_ORION means arch/arm/plat-orion.
But as far as i know, 370/XP does not actually use anything from
arch/arm/plat-orion. When kirkwood moves into mach-mvebu, it also will
not use any code from it, and i suspect dove is the same.
So maybe in a few cycles, when only mach-orion5x is left, we can merge
arch/arm/plat-orion into arch/arm/mach-orion5x and PLAT_ORION goes
away?
Or do we want to define that PLAT_ORION means any system which can
make use of mvebu drivers?
Andrew
next prev parent reply other threads:[~2014-02-18 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 10:29 [PATCH] net: ethernet: remove unneeded dependency of mvneta and update help text Thomas Petazzoni
2014-02-18 12:29 ` Jason Cooper
2014-02-18 12:45 ` Thomas Petazzoni
2014-02-18 12:52 ` Jason Cooper
2014-02-18 13:13 ` Thomas Petazzoni
2014-02-18 13:58 ` Andrew Lunn [this message]
2014-02-18 14:10 ` Thomas Petazzoni
2014-02-18 15:45 ` Ezequiel Garcia
2014-02-18 15:51 ` Thomas Petazzoni
2014-02-18 17:23 ` Ezequiel Garcia
2014-02-19 2:10 ` Jisheng Zhang
2014-02-19 8:08 ` Thomas Petazzoni
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=20140218135809.GD17984@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=ezequiel.garcia@free-electrons$(echo .)com \
--cc=gregory.clement@free-electrons$(echo .)com \
--cc=jason@lakedaemon$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sebastian.hesselbarth@gmail$(echo .)com \
--cc=thomas.petazzoni@free-electrons$(echo .)com \
/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