public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	"Paul E. McKenney" <paulmck@linux.ibm.com>
Subject: [rcu:rcu/next 27/86] drivers/base/core.c:102:9: error: implicit declaration of function 'lock_is_held'; did you mean 'lockref_get'?
Date: Tue, 13 Aug 2019 04:58:44 +0800	[thread overview]
Message-ID: <201908130428.TFrFvLFs%lkp@intel.com> (raw)

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

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
head:   eee850b8c265f38ab5feeb8fe6793b1b86eb77c7
commit: 4a3a5474b4c14fc6bc57b2d30cfbf20b54d54989 [27/86] driver/core: Convert to use built-in RCU list checking
config: parisc-allnoconfig (attached as .config)
compiler: hppa-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 4a3a5474b4c14fc6bc57b2d30cfbf20b54d54989
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=parisc 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/base/core.c: In function 'device_links_read_lock_held':
>> drivers/base/core.c:102:9: error: implicit declaration of function 'lock_is_held'; did you mean 'lockref_get'? [-Werror=implicit-function-declaration]
     return lock_is_held(&device_links_lock);
            ^~~~~~~~~~~~
            lockref_get
   cc1: some warnings being treated as errors

vim +102 drivers/base/core.c

    99	
   100	int device_links_read_lock_held(void)
   101	{
 > 102		return lock_is_held(&device_links_lock);
   103	}
   104	#endif /* !CONFIG_SRCU */
   105	

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 5479 bytes --]

                 reply	other threads:[~2019-08-12 21:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201908130428.TFrFvLFs%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=joel@joelfernandes.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.ibm.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