From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 1/3] net: Move MII out from under NET_CORE and hide it
Date: Tue, 18 Jun 2013 03:02:02 -0700 [thread overview]
Message-ID: <1371549722.2133.145.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1371522291.3495.63.camel@deadeye.wl.decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2537 bytes --]
On Tue, 2013-06-18 at 03:24 +0100, Ben Hutchings wrote:
> All drivers that select MII also need to select NET_CORE because MII
> depends on it. This is a bit ridiculous because NET_CORE is just a
> menu option that doesn't enable any code by itself.
>
> There is also no need for it to be a visible option, since its users
> all select it.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> arch/cris/arch-v10/drivers/Kconfig | 1 -
> arch/cris/arch-v32/drivers/Kconfig | 1 -
> drivers/net/Kconfig | 10 +++-------
> drivers/net/ethernet/3com/Kconfig | 1 -
> drivers/net/ethernet/Kconfig | 4 ----
> drivers/net/ethernet/adaptec/Kconfig | 1 -
> drivers/net/ethernet/adi/Kconfig | 1 -
> drivers/net/ethernet/allwinner/Kconfig | 1 -
> drivers/net/ethernet/amd/Kconfig | 2 --
> drivers/net/ethernet/atheros/Kconfig | 4 ----
> drivers/net/ethernet/broadcom/Kconfig | 2 --
> drivers/net/ethernet/cirrus/Kconfig | 1 -
> drivers/net/ethernet/davicom/Kconfig | 1 -
> drivers/net/ethernet/dec/tulip/Kconfig | 1 -
> drivers/net/ethernet/dlink/Kconfig | 1 -
> drivers/net/ethernet/faraday/Kconfig | 1 -
> drivers/net/ethernet/freescale/fs_enet/Kconfig | 1 -
> drivers/net/ethernet/icplus/Kconfig | 1 -
> drivers/net/ethernet/intel/Kconfig | 1 -
> drivers/net/ethernet/micrel/Kconfig | 4 ----
> drivers/net/ethernet/nuvoton/Kconfig | 1 -
> drivers/net/ethernet/oki-semi/pch_gbe/Kconfig | 1 -
> drivers/net/ethernet/packetengines/Kconfig | 1 -
> drivers/net/ethernet/rdc/Kconfig | 1 -
> drivers/net/ethernet/realtek/Kconfig | 3 ---
> drivers/net/ethernet/renesas/Kconfig | 1 -
> drivers/net/ethernet/sgi/Kconfig | 1 -
> drivers/net/ethernet/sis/Kconfig | 2 --
> drivers/net/ethernet/smsc/Kconfig | 5 -----
> drivers/net/ethernet/stmicro/stmmac/Kconfig | 1 -
> drivers/net/ethernet/via/Kconfig | 2 --
> drivers/net/usb/Kconfig | 4 ----
> drivers/staging/silicom/Kconfig | 1 -
> 33 files changed, 3 insertions(+), 61 deletions(-)
Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-18 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 2:21 [PATCH net-next 0/3] net driver dependency cleanup Ben Hutchings
2013-06-18 2:24 ` [PATCH net-next 1/3] net: Move MII out from under NET_CORE and hide it Ben Hutchings
2013-06-18 10:02 ` Jeff Kirsher [this message]
2013-06-20 5:23 ` David Miller
2013-06-18 2:27 ` [PATCH net-next 2/3] at91_ether: Do not select NET_CORE Ben Hutchings
2013-06-18 7:55 ` Nicolas Ferre
2013-06-20 5:23 ` David Miller
2013-06-18 2:37 ` [PATCH net-next 3/3] net: Add missing dependencies on NETDEVICES Ben Hutchings
2013-06-18 3:37 ` Ben Hutchings
2013-06-20 5:23 ` David Miller
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=1371549722.2133.145.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).