From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] net sched: printk message severity
Date: Mon, 17 May 2010 22:58:07 -0700 (PDT) [thread overview]
Message-ID: <20100517.225807.22051427.davem@davemloft.net> (raw)
In-Reply-To: <20100512163719.414013223@vyatta.com>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 12 May 2010 09:37:05 -0700
> The previous patch encourage me to go look at all the messages in
> the network scheduler and fix them. Many messages were missing
> any severity level. Some serious ones that should never happen
> were turned into WARN(), and the random noise messages that were
> handled changed to pr_debug().
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Applied.
next prev parent reply other threads:[~2010-05-18 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100512163704.780058547@vyatta.com>
2010-05-12 16:37 ` [PATCH 1/3] net sched: printk message severity Stephen Hemminger
2010-05-18 5:58 ` David Miller [this message]
2010-05-12 16:37 ` [PATCH 2/3] xfrm: add severity to printk Stephen Hemminger
2010-05-18 5:58 ` David Miller
2010-05-12 16:37 ` [PATCH 3/3] pfkey: " Stephen Hemminger
2010-05-18 5:58 ` David Miller
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=20100517.225807.22051427.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).