From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, "Dilger,
Andreas" <andreas.dilger@intel.com>,
linux-kernel@vger.kernel.org, "Drokin,
Oleg" <oleg.drokin@intel.com>,
kbuild-all@01.org, lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper
Date: Fri, 13 Nov 2015 18:33:31 +0530 [thread overview]
Message-ID: <20151113130331.GB18741@sudip-pc> (raw)
In-Reply-To: <CAKHNQQEW9ZcYrdowy5cFkJXqzEyoy+CseJg_3ge0QCC7=5oA3A@mail.gmail.com>
On Wed, Nov 11, 2015 at 11:03:34PM +0530, Shivani Bhardwaj wrote:
> On Wed, Nov 11, 2015 at 11:01 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Wed, Nov 11, 2015 at 10:51:36PM +0530, Shivani Bhardwaj wrote:
> >> On Wed, Nov 11, 2015 at 4:24 PM, kbuild test robot <lkp@intel.com> wrote:
<snip>
> >>
> >> I'm not getting any of these errors at compilation. I've checked
> >> thrice. Could you please tell what am I doing wrong so that I can
> >> avoid introducing errors in future patches?
> >
> > Use the .config provided, odds are you have lockdep enabled.
>
> Thanks Greg.
> I tried that. Still no errors. Any other suggestion?
while removing the wrapper you missed that cl_lock_lockdep_init() is:
static void cl_lock_lockdep_init(struct cl_lock *lock)
{
lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
}
if CONFIG_LOCKDEP is defined.
and if CONFIG_LOCKDEP is not defined then:
static void cl_lock_lockdep_init(struct cl_lock *lock)
{}
your patch is using lockdep_set_class_and_name() in both cases.
regards
sudip
next prev parent reply other threads:[~2015-11-13 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 10:21 [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper Shivani Bhardwaj
2015-11-11 10:54 ` 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 [this message]
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=20151113130331.GB18741@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=shivanib134@gmail.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