linux-kernel.vger.kernel.org archive mirror
 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:dev.2019.07.31a 66/123] drivers/base/core.c:102:9: error: implicit declaration of function 'lock_is_held'; did you mean 'lockref_get'?
Date: Thu, 8 Aug 2019 00:22:30 +0800	[thread overview]
Message-ID: <201908080026.WSAFx14k%lkp@intel.com> (raw)

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

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.07.31a
head:   71cf692f482ff45802352cf85a8880035fca9e52
commit: c9e4d3a2fee806436d2ad6f2cbccd3de25681a9d [66/123] acpi: Use built-in RCU list checking for acpi_ioremaps list
config: powerpc-allnoconfig (attached as .config)
compiler: powerpc-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 c9e4d3a2fee806436d2ad6f2cbccd3de25681a9d
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=powerpc 

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: 6287 bytes --]

                 reply	other threads:[~2019-08-07 16:23 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=201908080026.WSAFx14k%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;
as well as URLs for NNTP newsgroup(s).