mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
	oleg.drokin@intel.com, devel@driverdev.osuosl.org,
	andreas.dilger@intel.com, linux-kernel@vger.kernel.org,
	lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging: lustre: cl_lock: Remove cl_lock_lockdep_init wrapper
Date: Wed, 11 Nov 2015 18:54:41 +0800	[thread overview]
Message-ID: <201511111859.mIw4mICa%fengguang.wu@intel.com> (raw)
In-Reply-To: <1447237306-46901-1-git-send-email-shivanib134@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2939 bytes --]

Hi Shivani,

[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.3 next-20151111]

url:    https://github.com/0day-ci/linux/commits/Shivani-Bhardwaj/staging-lustre-cl_lock-Remove-cl_lock_lockdep_init-wrapper/20151111-182452
config: m68k-allyesconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=m68k 

All errors (new ones prefixed by >>):

   In file included from include/linux/spinlock_types.h:18:0,
                    from include/linux/spinlock.h:81,
                    from include/linux/mmzone.h:7,
                    from include/linux/gfp.h:5,
                    from include/linux/slab.h:14,
                    from drivers/staging/lustre/lustre/obdclass/../include/obd_support.h:40,
                    from drivers/staging/lustre/lustre/obdclass/../include/obd_class.h:39,
                    from drivers/staging/lustre/lustre/obdclass/cl_lock.c:43:
   drivers/staging/lustre/lustre/obdclass/cl_lock.c: In function 'cl_lock_alloc':
>> drivers/staging/lustre/lustre/obdclass/cl_lock.c:379:37: error: 'cl_lock_key' undeclared (first use in this function)
      lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
                                        ^
   include/linux/lockdep.h:401:15: note: in definition of macro 'lockdep_set_class_and_name'
      do { (void)(key); (void)(name); } while (0)
                  ^
   drivers/staging/lustre/lustre/obdclass/cl_lock.c:379:37: note: each undeclared identifier is reported only once for each function it appears in
      lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
                                        ^
   include/linux/lockdep.h:401:15: note: in definition of macro 'lockdep_set_class_and_name'
      do { (void)(key); (void)(name); } while (0)
                  ^
   drivers/staging/lustre/lustre/obdclass/cl_lock.c: At top level:
   drivers/staging/lustre/lustre/obdclass/cl_lock.c:166:13: warning: 'cl_lock_lockdep_init' defined but not used [-Wunused-function]
    static void cl_lock_lockdep_init(struct cl_lock *lock)
                ^

vim +/cl_lock_key +379 drivers/staging/lustre/lustre/obdclass/cl_lock.c

   373			lockdep_set_class(&lock->cll_guard, &cl_lock_guard_class);
   374			init_waitqueue_head(&lock->cll_wq);
   375			head = obj->co_lu.lo_header;
   376			CS_LOCKSTATE_INC(obj, CLS_NEW);
   377			CS_LOCK_INC(obj, total);
   378			CS_LOCK_INC(obj, create);
 > 379			lockdep_set_class_and_name(lock, &cl_lock_key, "EXT");
   380			list_for_each_entry(obj, &head->loh_layers,
   381						co_lu.lo_linkage) {
   382				int err;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 35206 bytes --]

  reply	other threads:[~2015-11-11 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 10:21 Shivani Bhardwaj
2015-11-11 10:54 ` kbuild test robot [this message]
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=201511111859.mIw4mICa%fengguang.wu@intel.com \
    --to=lkp@intel.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

all inboxes | Powered by JetHome®