From: Shivani Bhardwaj <shivanib134@gmail.com>
To: gregkh@linuxfoundation.org
Cc: andreas.dilger@intel.com, oleg.drokin@intel.com,
lustre-devel@lists.lustre.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper
Date: Wed, 11 Nov 2015 15:51:46 +0530 [thread overview]
Message-ID: <1447237306-46901-1-git-send-email-shivanib134@gmail.com> (raw)
Remove the wrapper function cl_lock_lockdep_init() and replace its only
call with the function it wrapped.
Signed-off-by: Shivani Bhardwaj <shivanib134@gmail.com>
---
drivers/staging/lustre/lustre/obdclass/cl_lock.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/staging/lustre/lustre/obdclass/cl_lock.c b/drivers/staging/lustre/lustre/obdclass/cl_lock.c
index 1836dc0..813d0ab 100644
--- a/drivers/staging/lustre/lustre/obdclass/cl_lock.c
+++ b/drivers/staging/lustre/lustre/obdclass/cl_lock.c
@@ -147,11 +147,6 @@ static void cl_lock_trace0(int level, const struct lu_env *env,
#ifdef CONFIG_LOCKDEP
static struct lock_class_key cl_lock_key;
-static void cl_lock_lockdep_init(struct cl_lock *lock)
-{
- lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
-}
-
static void cl_lock_lockdep_acquire(const struct lu_env *env,
struct cl_lock *lock, __u32 enqflags)
{
@@ -381,7 +376,7 @@ static struct cl_lock *cl_lock_alloc(const struct lu_env *env,
CS_LOCKSTATE_INC(obj, CLS_NEW);
CS_LOCK_INC(obj, total);
CS_LOCK_INC(obj, create);
- cl_lock_lockdep_init(lock);
+ lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
list_for_each_entry(obj, &head->loh_layers,
co_lu.lo_linkage) {
int err;
--
2.1.0
next reply other threads:[~2015-11-11 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 10:21 Shivani Bhardwaj [this message]
2015-11-11 10:54 ` [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper kbuild test robot
2015-11-11 17:21 ` Shivani Bhardwaj
2015-11-11 17:31 ` Greg KH
2015-11-11 17:33 ` Shivani Bhardwaj
2015-11-13 13:03 ` Sudip Mukherjee
2015-11-13 13:06 ` Shivani Bhardwaj
2015-11-13 0:59 ` [lustre-devel] " Dilger, Andreas
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=1447237306-46901-1-git-send-email-shivanib134@gmail.com \
--to=shivanib134@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.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