From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: Alexander Zapatka <alexzapatka@hotmail.com>
Cc: netdev@oss.sgi.com
Subject: Re: suggested forcedeth updates....
Date: Wed, 19 Nov 2003 12:48:45 +0100 [thread overview]
Message-ID: <20031119124845.B7622@sygehus.dk> (raw)
In-Reply-To: <BAY2-F101QTmReozTIA0001027c@hotmail.com>; from alexzapatka@hotmail.com on Mon, Nov 17, 2003 at 11:07:15PM -0500
On Mon, Nov 17, 2003 at 11:07:15PM -0500, Alexander Zapatka wrote:
> that way you can modprobe/insmod with debug=1 and debuging works... or you
> can just load it, or load it with debug=0 and no debuging info is printed.
>
> just thought it might be a nice addition.
Even better would be to use the NETIF_MSG_* flags defined in
linux/netdevice.c and to be able to use ethtool to change the setting at
runtime.
--
Regards,
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2003-11-19 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 4:07 suggested forcedeth updates Alexander Zapatka
2003-11-19 11:48 ` Rask Ingemann Lambertsen [this message]
2003-11-19 14:06 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-11-19 15:06 Alexander Zapatka
2003-11-20 17:04 ` Rask Ingemann Lambertsen
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=20031119124845.B7622@sygehus.dk \
--to=rask@sygehus.dk \
--cc=alexzapatka@hotmail.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).