net sched: printk message severity
authorstephen hemminger <shemminger@vyatta.com>
Wed, 12 May 2010 06:37:05 +0000 (06:37 +0000)
committerDavid S. Miller <davem@davemloft.net>
Tue, 18 May 2010 06:23:12 +0000 (23:23 -0700)
commit6ff9c3644e72bfac20844e0155c2cc8108602820
tree81a8ce88d6f0f91ff7f68b234c2d20d6a0d8745f
parent00c60a8312c235cac1c879b620ecb71413e9245d
net sched: printk message severity

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>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/sched/act_api.c
net/sched/act_gact.c
net/sched/act_ipt.c
net/sched/act_mirred.c
net/sched/act_pedit.c
net/sched/act_simple.c
net/sched/cls_u32.c
net/sched/ematch.c