summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorLen Brown <len.brown@intel.com>2008-03-26 13:29:32 -0400
committerLen Brown <len.brown@intel.com>2008-03-26 14:22:20 -0400
commit33fd7afd66ffdc6addf1b085fe6403b6af532f8e (patch)
tree81bd5de11fae59e7c86cba9378ca03b71569c0d0 /include
parent05dda977f2574c3341abef9b74c27d2b362e1e3a (diff)
downloadop-kernel-dev-33fd7afd66ffdc6addf1b085fe6403b6af532f8e.zip
op-kernel-dev-33fd7afd66ffdc6addf1b085fe6403b6af532f8e.tar.gz
pnpacpi: reduce printk severity for "pnpacpi: exceeded the max number of ..."
We have been printing these messages at KERN_ERR since 2.6.24, per http://bugzilla.kernel.org/show_bug.cgi?id=9535 But KERN_ERR pops up on a console booted with "quiet" and causes users to get alarmed and file bugs about the message itself: https://bugzilla.redhat.com/show_bug.cgi?id=436589 So reduce the severity of these messages to KERN_WARNING, which is not printed by "quiet". This message will still be seen without "quiet", but a lot of messages are printed in that mode and it will be less likely to cause undue alarm. We could go all the way to KERN_DEBUG, but this is a real warning after all, so it seems prudent not to require "debug" to see it. Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud