From: Jeff Garzik <jeff@garzik.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Ayyappan Veeraiyan <ayyappan.veeraiyan@intel.com>,
netdev@vger.kernel.org, arjan@linux.intel.com,
akpm@linux-foundation.org, auke-jan.h.kok@intel.com,
hch@infradead.org, nhorman@tuxdriver.com, inaky@linux.intel.com,
mb@bu3sch.de, john.ronciak@intel.com
Subject: Re: [PATCH 1/1]ixgbe: Driver for Intel 82598 based 10GbE PCI Express family of adapters
Date: Fri, 27 Jul 2007 09:52:02 -0400 [thread overview]
Message-ID: <46A9F882.3000208@garzik.org> (raw)
In-Reply-To: <46A91EA5.9060005@linux-foundation.org>
Stephen Hemminger wrote:
> Using module parameter for per device settings is bad idea.
> Please extend existing interfaces like ethtool, etc rather than committing
> to a bad inflexible API.
I agreed with Stephen's comments here.
In general, net driver policy is to use ethtool (per-interface
granularity) rather than module options.
Jeff
next prev parent reply other threads:[~2007-07-27 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 20:08 [PATCH 0/1] ixgbe: Support for Intel(R) 10GbE PCI Express adapters - Take #3 Ayyappan.Veeraiyan
2007-07-26 20:09 ` [PATCH 1/1]ixgbe: Driver for Intel 82598 based 10GbE PCI Express family of adapters Ayyappan Veeraiyan
2007-07-26 22:22 ` Stephen Hemminger
2007-07-27 13:52 ` Jeff Garzik [this message]
2007-07-27 19:45 ` Veeraiyan, Ayyappan
2007-07-27 20:01 ` Jeff Garzik
2007-07-27 20:06 ` Veeraiyan, Ayyappan
-- strict thread matches above, loose matches on Subject: below --
2007-07-10 17:45 [PATCH 0/1] ixgbe: Support for Intel(R) 10GbE PCI Express adapters - Take #2 Ayyappan.Veeraiyan
2007-07-10 17:49 ` [PATCH 1/1]ixgbe: Driver for Intel 82598 based 10GbE PCI Express family of adapters Ayyappan Veeraiyan
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=46A9F882.3000208@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=ayyappan.veeraiyan@intel.com \
--cc=hch@infradead.org \
--cc=inaky@linux.intel.com \
--cc=john.ronciak@intel.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=shemminger@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.