SUNRPC: Use KERN_DEFAULT for debugging printk's
authorChuck Lever <chuck.lever@oracle.com>
Wed, 15 Feb 2012 21:35:08 +0000 (16:35 -0500)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Thu, 16 Feb 2012 19:55:30 +0000 (14:55 -0500)
commitdbb9c2a22d32492544765e798386daa2d9da27d2
tree997ad46ec944ec99fcb95f566825c3ea9506ff50
parent15a4520621824a3c2eb2de2d1f3984bc1663d3c8
SUNRPC: Use KERN_DEFAULT for debugging printk's

Our dprintk() debugging facility doesn't specify any verbosity level
for it's printk() calls, but it should.

The default verbosity for printk's is KERN_DEFAULT.  You might argue
that these are debugging printk's and thus the verbosity should be
KERN_DEBUG.  That would mean that to see NFS and SUNRPC debugging
output an admin would also have to boost the syslog verbosity, which
would be insufferably noisy.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
include/linux/sunrpc/debug.h