public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@primarydata.com>
To: trond.myklebust@primarydata.com
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] lockd/sunrpc: eliminate some pointless macro indirection
Date: Mon, 17 Nov 2014 16:58:02 -0500	[thread overview]
Message-ID: <1416261485-24686-1-git-send-email-jlayton@primarydata.com> (raw)

We currently have a number of legacy macros in the sunrpc code, as well
as a smaller number in lockd that are used to indicate whether debugging
support is compiled in or not.

This hash always seemed like pointless indirection as those symbols
always reflect the value of a CONFIG_* value. This patchset just removes
those macros in favor of their CONFIG_* equivalents.

Jeff Layton (3):
  lockd: eliminate LOCKD_DEBUG
  sunrpc: eliminate RPC_DEBUG
  sunrpc: eliminate RPC_TRACEPOINTS

 fs/lockd/svclock.c                      |  2 +-
 include/linux/lockd/debug.h             |  6 +-----
 include/linux/sunrpc/auth.h             |  2 +-
 include/linux/sunrpc/debug.h            | 18 +++---------------
 include/linux/sunrpc/sched.h            |  8 ++++----
 include/uapi/linux/nfsd/debug.h         |  2 +-
 net/sunrpc/auth.c                       |  4 ++--
 net/sunrpc/auth_generic.c               |  2 +-
 net/sunrpc/auth_gss/auth_gss.c          |  2 +-
 net/sunrpc/auth_gss/gss_generic_token.c |  2 +-
 net/sunrpc/auth_gss/gss_krb5_crypto.c   |  2 +-
 net/sunrpc/auth_gss/gss_krb5_keys.c     |  2 +-
 net/sunrpc/auth_gss/gss_krb5_mech.c     |  2 +-
 net/sunrpc/auth_gss/gss_krb5_seal.c     |  2 +-
 net/sunrpc/auth_gss/gss_krb5_seqnum.c   |  2 +-
 net/sunrpc/auth_gss/gss_krb5_unseal.c   |  2 +-
 net/sunrpc/auth_gss/gss_krb5_wrap.c     |  2 +-
 net/sunrpc/auth_gss/gss_mech_switch.c   |  2 +-
 net/sunrpc/auth_gss/gss_rpc_xdr.h       |  2 +-
 net/sunrpc/auth_gss/svcauth_gss.c       |  2 +-
 net/sunrpc/auth_null.c                  |  4 ++--
 net/sunrpc/auth_unix.c                  |  2 +-
 net/sunrpc/backchannel_rqst.c           |  2 +-
 net/sunrpc/clnt.c                       |  6 +++---
 net/sunrpc/rpcb_clnt.c                  |  2 +-
 net/sunrpc/sched.c                      |  4 ++--
 net/sunrpc/sunrpc_syms.c                |  4 ++--
 net/sunrpc/svc.c                        |  2 +-
 net/sunrpc/sysctl.c                     |  2 +-
 net/sunrpc/xprt.c                       |  2 +-
 net/sunrpc/xprtrdma/rpc_rdma.c          |  4 ++--
 net/sunrpc/xprtrdma/transport.c         |  8 ++++----
 net/sunrpc/xprtrdma/verbs.c             |  8 ++++----
 net/sunrpc/xprtsock.c                   |  8 ++++----
 34 files changed, 55 insertions(+), 71 deletions(-)

-- 
2.1.0


             reply	other threads:[~2014-11-17 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 21:58 Jeff Layton [this message]
2014-11-17 21:58 ` [PATCH 1/3] lockd: eliminate LOCKD_DEBUG Jeff Layton
2014-11-17 21:58 ` [PATCH 2/3] sunrpc: eliminate RPC_DEBUG Jeff Layton
2014-11-18 13:40   ` Anna Schumaker
2014-11-18 13:54     ` Jeff Layton
2014-11-18 14:01       ` Anna Schumaker
2014-11-18 17:08         ` Anna Schumaker
2014-11-17 21:58 ` [PATCH 3/3] sunrpc: eliminate RPC_TRACEPOINTS Jeff Layton

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=1416261485-24686-1-git-send-email-jlayton@primarydata.com \
    --to=jlayton@primarydata.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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