linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: ceph-devel@vger.kernel.org, linux-block@vger.kernel.org
Cc: Ilya Dryomov <idryomov@gmail.com>,
	Dongsheng Yang <dongsheng.yang@easystack.cn>,
	Jens Axboe <axboe@kernel.dk>, Jeff Layton <jlayton@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH V2 0/6] ceph: Use more generic logging
Date: Sun, 16 Aug 2020 18:34:03 -0700	[thread overview]
Message-ID: <cover.1597626802.git.joe@perches.com> (raw)

Convert the dout macro to the normal pr_debug.
Convert embedded function names in these changes to %s, __func__
Remove the dout macro definitions

Joe Perches (6):
  ceph: Use generic debugging facility
  ceph: Remove embedded function names from pr_debug uses
  net: ceph:  Use generic debugging facility
  net: ceph: Remove embedded function names from pr_debug uses
  rbd: Use generic debugging facility
  ceph_debug: Remove now unused dout macro definitions

 drivers/block/rbd.c             | 231 +++++++-------
 fs/ceph/addr.c                  | 266 ++++++++--------
 fs/ceph/cache.c                 |  22 +-
 fs/ceph/caps.c                  | 533 ++++++++++++++++----------------
 fs/ceph/debugfs.c               |   4 +-
 fs/ceph/dir.c                   | 141 ++++-----
 fs/ceph/export.c                |  36 +--
 fs/ceph/file.c                  | 170 +++++-----
 fs/ceph/inode.c                 | 338 ++++++++++----------
 fs/ceph/ioctl.c                 |   6 +-
 fs/ceph/locks.c                 |  42 +--
 fs/ceph/mds_client.c            | 374 +++++++++++-----------
 fs/ceph/mdsmap.c                |  16 +-
 fs/ceph/metric.c                |   4 +-
 fs/ceph/quota.c                 |   4 +-
 fs/ceph/snap.c                  | 135 ++++----
 fs/ceph/super.c                 |  67 ++--
 fs/ceph/xattr.c                 |  64 ++--
 include/linux/ceph/ceph_debug.h |  30 --
 include/linux/ceph/messenger.h  |   2 +-
 net/ceph/auth.c                 |  21 +-
 net/ceph/auth_none.c            |   4 +-
 net/ceph/auth_x.c               |  85 ++---
 net/ceph/buffer.c               |   6 +-
 net/ceph/ceph_common.c          |  18 +-
 net/ceph/cls_lock_client.c      |  32 +-
 net/ceph/crypto.c               |   8 +-
 net/ceph/debugfs.c              |   4 +-
 net/ceph/messenger.c            | 330 ++++++++++----------
 net/ceph/mon_client.c           |  99 +++---
 net/ceph/msgpool.c              |  14 +-
 net/ceph/osd_client.c           | 393 ++++++++++++-----------
 net/ceph/osdmap.c               | 101 +++---
 net/ceph/pagevec.c              |  10 +-
 34 files changed, 1835 insertions(+), 1775 deletions(-)

-- 
2.26.0


             reply	other threads:[~2020-08-17  1:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17  1:34 Joe Perches [this message]
2020-08-17  1:34 ` [PATCH V2 5/6] rbd: Use generic debugging facility Joe Perches

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=cover.1597626802.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=axboe@kernel.dk \
    --cc=ceph-devel@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=dongsheng.yang@easystack.cn \
    --cc=idryomov@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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).