From: Weston Andros Adamson <dros@netapp.com>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject:
Date: Thu, 26 Jan 2012 13:32:21 -0500 [thread overview]
Message-ID: <1327602743-1152-1-git-send-email-dros@netapp.com> (raw)
End users probably find it confusing to see messages from the nfs subsystem
that aren't labeled as such. These patches modify all printks (not d*printks)
to start with "NFS:"
I separated this in to two patches:
- printks that obvisouly need this as they have no context to inform a user
that the message is related to NFS
- printks that do have some context (such as printing __func__), but are
changed to start with "NFS:" for consistency
next reply other threads:[~2012-01-26 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 18:32 Weston Andros Adamson [this message]
2012-01-26 18:32 ` [PATCH 1/2] NFS: printks in fs/nfs/ should start with NFS: Weston Andros Adamson
2012-01-26 18:32 ` [PATCH 2/2] NFS: start printks w/ NFS: even if __func__ shown Weston Andros Adamson
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=1327602743-1152-1-git-send-email-dros@netapp.com \
--to=dros@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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).