From: Keith Owens <kaos@ocs.com.au>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, "David S. Miller" <davem@redhat.com>
Subject: Re: PATCH: ethtool MII helpers
Date: Mon, 11 Jun 2001 16:10:18 +1000 [thread overview]
Message-ID: <12459.992239818@ocs4.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 11 Jun 2001 08:59:10 +0300." <Pine.LNX.4.33.0106110852570.23217-100000@netcore.fi>
On Mon, 11 Jun 2001 08:59:10 +0300 (EEST),
Pekka Savola <pekkas@netcore.fi> wrote:
>+MODULE_PARM_DESC(debug, "EPIC/100 debug level (0-5)");
>+MODULE_PARM_DESC(max_interrupt_work, "EPIC/100 maximum events handled per interrupt");
>I recall some discussion on a list (can't find it now) that driver
>specific comment like "EPIC/100" here notification on all _DESC's would be
>removed to a separate MODULE_ to make the comments more generic?
MODULE_DESCRIPTION("EPIC/100 some text") would be better.
next prev parent reply other threads:[~2001-06-11 6:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 17:34 PATCH: ethtool MII helpers Jeff Garzik
2001-06-11 5:59 ` Pekka Savola
2001-06-11 6:10 ` Keith Owens [this message]
2001-06-12 17:09 ` Bogdan Costescu
2001-06-12 17:40 ` Jeff Garzik
2001-06-12 18:40 ` PATCH: ethtool MII helpers (vers 2) Jeff Garzik
2001-06-13 15:29 ` PATCH: ethtool MII helpers Bogdan Costescu
2001-06-13 16:56 ` Donald Becker
2001-06-13 20:24 ` Jeff Garzik
2001-06-15 17:22 ` Bogdan Costescu
2001-06-22 5:10 ` Chris Wedgwood
2001-06-22 5:24 ` Jeff Garzik
2001-06-22 5:34 ` Chris Wedgwood
2001-06-22 5:58 ` Jeff Garzik
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=12459.992239818@ocs4.ocs-net \
--to=kaos@ocs.com.au \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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.