netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@hockin.org>
To: Marc Herbert <marc.herbert@free.fr>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] ethtool semantics
Date: Mon, 14 Jun 2004 10:01:38 -0700	[thread overview]
Message-ID: <20040614170138.GA32594@hockin.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0406141458270.16762@fcat>

On Mon, Jun 14, 2004 at 03:11:15PM +0200, Marc Herbert wrote:
> > That is absolutely the correct thing to do, module parameters for
> > link settings are %100 deprecated, people need to use ethtool for
> > everything.
> 
> This is precisely the reason why I am concerned about having "rich"
> ethtool semantics. A unified, standard interface is great,... as long
> it does not leave behind some features, like setting the advertised
> values in autoneg. As a user of these features, I hope driver
> developers will NOT remove those module_param features that cannot
> migrated to ethtool.

So propose a sane semantic that handles all three cases:
* autoneg on
* autoneg off
* autoneg on but limited

  reply	other threads:[~2004-06-14 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 21:28 [RFC] ethtool semantics Roger Luethi
2004-06-07 21:57 ` David S. Miller
2004-06-07 23:43   ` Marc Herbert
2004-06-08 21:08   ` Roger Luethi
2004-06-09 21:09     ` Bill Davidsen
2004-06-09 21:38       ` Roger Luethi
2004-06-09 22:12         ` David S. Miller
2004-06-14 13:11           ` Marc Herbert
2004-06-14 17:01             ` Tim Hockin [this message]
2004-06-14 19:32               ` Marc Herbert
2004-06-14 19:42               ` Roger Luethi

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=20040614170138.GA32594@hockin.org \
    --to=thockin@hockin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.herbert@free.fr \
    --cc=netdev@oss.sgi.com \
    /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).