netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Feldman <sfeldma@pobox.com>
To: Ganesh Venkatesan <ganesh.venkatesan@intel.com>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [patch 2/5 2.4] e1000 - Fix MODULE_PARM, module_param and module_param_array usage
Date: Fri, 17 Sep 2004 19:42:17 -0700	[thread overview]
Message-ID: <1095475337.3496.5.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0409170218100.15233-100000@isotope.jf.intel.com>

What's this patch really about?

The only real change I see is the default ITR going from 8000 back to 1
(= dynamic mode).  What's this got to do with MODULE_PARAM, etc?  BTW,
wasn't there a big change to go from 1 to 8000.  Now this undoes that?

The rest of the changes look like someone is messing up the
whitespacing.  Why?

-scott

      reply	other threads:[~2004-09-18  2:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17  9:55 [patch 2/5 2.4] e1000 - Fix MODULE_PARM, module_param and module_param_array usage Ganesh Venkatesan
2004-09-18  2:42 ` Scott Feldman [this message]

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=1095475337.3496.5.camel@localhost.localdomain \
    --to=sfeldma@pobox.com \
    --cc=ganesh.venkatesan@intel.com \
    --cc=jgarzik@pobox.com \
    --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).