All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: David Miller <davem@davemloft.net>
Cc: dwmw2@infradead.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org,
	thomas.petazzoni@free-electrons.com, shemminger@vyatta.com,
	jeff@garzik.org, netdev@vger.kernel.org
Subject: Re: [patch 12/12] Configure out ethtool support
Date: Thu, 31 Jul 2008 10:36:31 -0500	[thread overview]
Message-ID: <1217518591.3657.27.camel@calx> (raw)
In-Reply-To: <20080731.034737.154058020.davem@davemloft.net>


On Thu, 2008-07-31 at 03:47 -0700, David Miller wrote:
> I especially appreciate that you still haven't accepted the plain fact
> that CONFIG_ETHTOOL needs to be selected by CONFIG_INET.

So far the following features have been mentioned as being critically
dependent on ethtool:

- bridging
- bonding
- LRO
- netfilter (really?)
- IPv6 (really?)

And yet every single one of these is currently a config option, so your
above statement is still looking awfully dubious. At this point I'd
suggest that you've painted yourself into a corner where all these
options must also actually be mandatory, but I'm afraid you might
secretly want to do that anyway.

> I definitely see the next consequence of the CONFIG_ETHTOOL stuff, and
> that's a set of ifdef'ola in all the drivers to config out the
> per-driver ethtool support code.

If someone shows up with such a patch for a Xylinx or ARM SOC device,
you probably should take it. If the patch is instead for a 10Gb PCIe
device, I suggest you don't. (At least not until that sort of thing
becomes standard embedded kit.)

-- 
Mathematics is the supreme nostalgia of our time.


  reply	other threads:[~2008-07-31 15:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 19:39 [patch 12/12] Configure out ethtool support akpm
2008-07-30 20:37 ` Stephen Hemminger
2008-07-30 20:48   ` Thomas Petazzoni
2008-07-30 21:01     ` Stephen Hemminger
2008-07-30 21:35       ` Thomas Petazzoni
2008-07-30 21:48         ` Andrew Morton
2008-07-30 21:52           ` Thomas Petazzoni
2008-07-30 22:04             ` Andrew Morton
2008-07-30 23:35               ` Roland Dreier
2008-07-30 21:57           ` David Miller
2008-07-30 22:13             ` Andrew Morton
2008-07-30 22:33               ` David Miller
2008-07-31 10:39               ` David Woodhouse
2008-07-31 10:43                 ` David Miller
2008-07-31 10:49                   ` David Woodhouse
2008-07-31 10:47                 ` David Miller
2008-07-31 15:36                   ` Matt Mackall [this message]
2008-07-31 15:59                     ` Stephen Hemminger
2008-07-31 16:11                       ` Matt Mackall
2008-07-31 18:17                     ` Evgeniy Polyakov
2008-07-30 21:35 ` David Miller
2008-07-30 21:44   ` Andrew Morton
2008-07-30 22:24   ` Matt Mackall
2008-07-30 22:37     ` David Miller
2008-07-30 23:05       ` Matt Mackall
2008-07-30 23:21         ` David Miller
2008-07-31  1:10           ` Matt Mackall
2008-07-31  1:23             ` David Miller
2008-07-31 10:22               ` Kalle Valo

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=1217518591.3657.27.camel@calx \
    --to=mpm@selenic.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.