linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Holton <fholton@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Frank Holton <fholton@gmail.com>
Subject: [PATCH] Btrfs syslog output prefix fixes
Date: Mon, 11 Nov 2013 02:27:14 -0500	[thread overview]
Message-ID: <1384154835-7037-1-git-send-email-fholton@gmail.com> (raw)

I've gone through the code and tried to find anywhere that prints to
the syslog and make sure that it uses the proper btrfs: prefix. This helps
users find the relevant lines for btrfs and makes sure a grep will return all
of the output from btrfs.

Frank Holton (1):
  Btrfs: Fixup usage of btrfs: prefix in syslog

 fs/btrfs/compression.c      |    4 ++--
 fs/btrfs/ctree.c            |   14 +++++++-------
 fs/btrfs/ctree.h            |    2 +-
 fs/btrfs/delayed-inode.c    |    4 ++--
 fs/btrfs/disk-io.c          |   34 +++++++++++++++++-----------------
 fs/btrfs/extent-tree.c      |    6 +++---
 fs/btrfs/extent_io.c        |   40 ++++++++++++++++++++--------------------
 fs/btrfs/file-item.c        |    2 +-
 fs/btrfs/free-space-cache.c |    6 +++---
 fs/btrfs/inode.c            |    6 +++---
 fs/btrfs/ioctl.c            |    6 +++---
 fs/btrfs/lzo.c              |    6 +++---
 fs/btrfs/ordered-data.c     |    6 +++---
 fs/btrfs/qgroup.c           |    4 ++--
 fs/btrfs/reada.c            |    4 ++--
 fs/btrfs/root-tree.c        |    2 +-
 fs/btrfs/scrub.c            |   10 +++++-----
 fs/btrfs/super.c            |   12 ++++++------
 18 files changed, 84 insertions(+), 84 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2013-11-11  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11  7:27 Frank Holton [this message]
2013-11-11  7:27 ` [PATCH] Btrfs: Fixup usage of btrfs: prefix in syslog Frank Holton
2013-11-12 16:17   ` David Sterba

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=1384154835-7037-1-git-send-email-fholton@gmail.com \
    --to=fholton@gmail.com \
    --cc=linux-btrfs@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).