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 v2 0/2] Change printk to btrfs_* where applicable
Date: Tue, 12 Nov 2013 19:22:51 -0500	[thread overview]
Message-ID: <1384302173-32075-1-git-send-email-fholton@gmail.com> (raw)

I've replaced pr_ and printk statments by btrfs_ output macros where I could
find a fs_info structure. There may be a few remaining cases where a fs_info
structure could be obtained from one of the inputs but I wasn't sure how.
For all the of the remaining pr_ and printk statements I've made sure that
the btrfs: prefix is present and correct.

The second patch is needed because of the way pr_debug is handled by the kernel.
When DEBUG is not defined pr_debug is removed and does not cause any output.
This patch defines btrfs_debug as noprintk when DEBUG is not defined which
matches the way pr_debug is handled.

Thanks

Frank Holton (2):
  Btrfs: convert printk and pr_ to btrfs_* and fix btrfs: prefix
  Btrfs: make btrfs_debug match pr_debug handling related to DEBUG

 fs/btrfs/backref.c               |   21 ++++----
 fs/btrfs/compression.c           |   11 ++--
 fs/btrfs/ctree.c                 |   14 ++---
 fs/btrfs/ctree.h                 |   10 +++-
 fs/btrfs/delayed-inode.c         |   10 ++--
 fs/btrfs/delayed-ref.c           |    3 +-
 fs/btrfs/dev-replace.c           |   28 +++++-----
 fs/btrfs/dir-item.c              |    6 +--
 fs/btrfs/disk-io.c               |   45 ++++++++--------
 fs/btrfs/extent-tree.c           |   12 ++---
 fs/btrfs/extent_io.c             |   83 ++++++++++++++++++------------
 fs/btrfs/file-item.c             |    4 +-
 fs/btrfs/free-space-cache.c      |   14 ++---
 fs/btrfs/inode.c                 |   12 ++---
 fs/btrfs/ioctl.c                 |   28 +++++-----
 fs/btrfs/lzo.c                   |    6 +--
 fs/btrfs/ordered-data.c          |    9 ++--
 fs/btrfs/qgroup.c                |   29 ++++++-----
 fs/btrfs/reada.c                 |   14 ++---
 fs/btrfs/relocation.c            |    4 +-
 fs/btrfs/root-tree.c             |    3 +-
 fs/btrfs/scrub.c                 |   27 +++++-----
 fs/btrfs/super.c                 |  105 ++++++++++++++++++--------------------
 fs/btrfs/tests/extent-io-tests.c |    3 +-
 fs/btrfs/transaction.c           |    4 +-
 fs/btrfs/uuid-tree.c             |   12 ++---
 fs/btrfs/volumes.c               |   70 ++++++++++++-------------
 27 files changed, 307 insertions(+), 280 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2013-11-13  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13  0:22 Frank Holton [this message]
2013-11-13  0:22 ` [PATCH v2 1/2] Btrfs: convert printk and pr_ to btrfs_* and fix btrfs: prefix Frank Holton
2013-11-14 15:25   ` David Sterba
2013-11-14 19:51     ` Frank Holton
2013-11-13  0:22 ` [PATCH 2/2] Btrfs: make btrfs_debug match pr_debug handling related to DEBUG Frank Holton

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=1384302173-32075-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).