From: Jeff Garzik <jeff@garzik.org>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ralf Baechle <ralf@linux-mips.org>,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Eliminate user-selectable CONFIG_MV643XX_ETH_[012]
Date: Tue, 20 Feb 2007 11:27:30 -0500 [thread overview]
Message-ID: <45DB2172.1070003@garzik.org> (raw)
In-Reply-To: <20070220121520.GA17927@xyzzy.farnsworth.org>
Dale Farnsworth wrote:
> From: Dale Farnsworth <dale@farnsworth.org>
>
> Remove the use of CONFIG_MV643XX_ETH_[012] variables on most
> platforms. Instead, platform-specific code enables the ports
> supported by the hardware. After this patch, these config
> variables are only used in arch/ppc, so also move them from
> drivers/net/Kconfig to arch/ppc/Kconfig.
>
> Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
>
> ---
> It was a mis-feature that the supported ports were ever user-selectable.
> Which ports the hardware supports should be specified by platform-specific
> code, not by the user.
>
> arch/mips/momentum/jaguar_atx/platform.c | 21 ---------------------
> arch/mips/momentum/ocelot_3/platform.c | 21 ---------------------
> arch/mips/momentum/ocelot_c/platform.c | 14 --------------
> arch/ppc/Kconfig | 15 +++++++++++++++
> drivers/net/Kconfig | 21 ---------------------
> 5 files changed, 15 insertions(+), 77 deletions(-)
ACK.
I'll let Paul, Ralf or Andrew push this one upstream.
next prev parent reply other threads:[~2007-02-20 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 12:15 [PATCH] Eliminate user-selectable CONFIG_MV643XX_ETH_[012] Dale Farnsworth
2007-02-20 12:22 ` Ralf Baechle
2007-02-20 16:27 ` Jeff Garzik [this message]
2007-02-20 17:00 ` Ralf Baechle
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=45DB2172.1070003@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=dale@farnsworth.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.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).