From: Richard Dawe <rich@phekda.gotadsl.co.uk>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>, netdev@oss.sgi.com
Subject: Re: [PATCH 4/5] r8169: ethtool message level control
Date: Sat, 12 Mar 2005 12:02:23 +0000 [thread overview]
Message-ID: <4232DA4F.5050804@phekda.gotadsl.co.uk> (raw)
In-Reply-To: <20050309113402.05d25e49@dxpl.pdx.osdl.net>
Hello.
Stephen Hemminger wrote:
> Add ethtool message level control support. This is the standard way
> to enable/disable console log messages. Also, ratelimit the too much
> work at interrupt message, so if under massive packet load the console
> doesn't get flooded.
>
> Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
>
> diff -Nru a/drivers/net/r8169.c b/drivers/net/r8169.c
> --- a/drivers/net/r8169.c 2005-03-09 11:25:04 -08:00
> +++ b/drivers/net/r8169.c 2005-03-09 11:25:04 -08:00
[snip]
> @@ -875,12 +885,26 @@
> spin_unlock_irqrestore(&tp->lock, flags);
> }
>
> +static u32 rtl8169_get_msglevel(struct net_device *dev)
> +{
> + struct rtl8169_private *tp = netdev_priv(dev);
> + return tp->msg_enable;
> +}
> +
> +static void rtl8169_set_msglevel(struct net_device *dev, u32 value)
> +{
> + struct rtl8169_private *tp = netdev_priv(dev);
> + tp->msg_enable = value;
> +}
> +
[snip]
When I posted a patch for message level support a couple of weeks ago
(and got a ton of corrective feedback), Francois asked that there be
whitespace separating the definitions from executable code in these
functions.
Bye, Rich =]
--
Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]
"You can't evaluate a man by logic alone."
-- McCoy, "I, Mudd", Star Trek
next prev parent reply other threads:[~2005-03-12 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 19:34 [PATCH 4/5] r8169: ethtool message level control Stephen Hemminger
2005-03-09 19:50 ` Jeff Garzik
2005-03-12 12:02 ` Richard Dawe [this message]
2005-03-12 14:33 ` Francois Romieu
2005-03-12 15:12 ` Richard Dawe
2005-03-12 12:30 ` Richard Dawe
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=4232DA4F.5050804@phekda.gotadsl.co.uk \
--to=rich@phekda.gotadsl.co.uk \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@osdl.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.