From: kbuild test robot <lkp@intel.com>
To: madhuparnabhowmik10@gmail.com
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
jiri@mellanox.com, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, joel@joelfernandes.org,
frextrite@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
paulmck@kernel.org,
Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
Subject: Re: [PATCH] net: core: devlink.c: Use built-in RCU list checking
Date: Mon, 24 Feb 2020 08:28:24 +0800 [thread overview]
Message-ID: <202002240820.cbyN0Rb5%lkp@intel.com> (raw)
In-Reply-To: <20200221165141.24630-1-madhuparnabhowmik10@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
[also build test ERROR on net/master linus/master v5.6-rc2 next-20200221]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/madhuparnabhowmik10-gmail-com/net-core-devlink-c-Use-built-in-RCU-list-checking/20200223-035655
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 732a0dee501f9a693c9a711730838129f4587041
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (git://gitmirror/llvm_project 1df947ab403a9ec3bb1bf4cd83610a997dc4f3bc)
reproduce:
# FIXME the reproduce steps for clang is not ready yet
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> net/core/devlink.c:2111:22: error: use of undeclared identifier 'devlink'
lockdep_is_held(&devlink->lock)) {
^
1 error generated.
vim +/devlink +2111 net/core/devlink.c
2103
2104 static struct devlink_dpipe_table *
2105 devlink_dpipe_table_find(struct list_head *dpipe_tables,
2106 const char *table_name)
2107 {
2108 struct devlink_dpipe_table *table;
2109
2110 list_for_each_entry_rcu(table, dpipe_tables, list,
> 2111 lockdep_is_held(&devlink->lock)) {
2112 if (!strcmp(table->name, table_name))
2113 return table;
2114 }
2115 return NULL;
2116 }
2117
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 72192 bytes --]
next prev parent reply other threads:[~2020-02-24 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 16:51 [PATCH] net: core: devlink.c: Use built-in RCU list checking madhuparnabhowmik10
2020-02-21 17:20 ` Jiri Pirko
2020-02-21 17:35 ` Madhuparna Bhowmik
2020-02-21 17:54 ` Jiri Pirko
2020-02-21 18:00 ` Madhuparna Bhowmik
2020-02-23 11:03 ` Madhuparna Bhowmik
2020-02-23 18:19 ` Jiri Pirko
2020-02-24 0:28 ` kbuild test robot [this message]
2020-02-24 9:30 madhuparnabhowmik10
2020-02-24 10:52 ` Jiri Pirko
2020-02-25 12:09 ` Madhuparna Bhowmik
2020-02-25 12:27 madhuparnabhowmik10
2020-02-25 13:06 ` Jiri Pirko
2020-02-27 0:59 ` David Miller
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=202002240820.cbyN0Rb5%lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=frextrite@gmail.com \
--cc=jiri@mellanox.com \
--cc=joel@joelfernandes.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
/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).