All of the debug messages in reconnect_path() use dprintk(), except for
one. Users have no idea what "reconnect_path: npd != pd" means, or how
to act on it. This message without the other dprintk() output is near to
useless anyway, so use dprintk() instead of printk() for it.

Signed-off-by: Niels de Vos <nde...@redhat.com>
---
 fs/exportfs/expfs.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/exportfs/expfs.c b/fs/exportfs/expfs.c
index a235f00..49ce614 100644
--- a/fs/exportfs/expfs.c
+++ b/fs/exportfs/expfs.c
@@ -189,7 +189,7 @@ reconnect_path(struct vfsmount *mnt, struct dentry 
*target_dir, char *nbuf)
                        if (npd == pd)
                                noprogress = 0;
                        else
-                               printk("%s: npd != pd\n", __func__);
+                               dprintk("%s: npd != pd\n", __func__);
                        dput(npd);
                        dput(ppd);
                        if (IS_ROOT(pd)) {
-- 
1.7.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to