From: kernel test robot <lkp@intel.com>
To: Dmitry Skorodumov <dskr99@gmail.com>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Dmitry Skorodumov <skorodumov.dmitry@huawei.com>,
Xiao Liang <shaw.leon@gmail.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Stanislav Fomichev <sdf@fomichev.me>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net 2/3] ipvlan: Common code from v6/v4 validator_event
Date: Wed, 21 Jan 2026 23:33:32 +0800 [thread overview]
Message-ID: <202601220042.cudmSYUb-lkp@intel.com> (raw)
In-Reply-To: <20260120161852.639238-3-skorodumov.dmitry@huawei.com>
Hi Dmitry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net/main]
url: https://github.com/intel-lab-lkp/linux/commits/Dmitry-Skorodumov/ipvlan-const-specifier-for-functions-that-use-iaddr/20260121-021651
base: net/main
patch link: https://lore.kernel.org/r/20260120161852.639238-3-skorodumov.dmitry%40huawei.com
patch subject: [PATCH net 2/3] ipvlan: Common code from v6/v4 validator_event
config: csky-randconfig-r073-20260121 (https://download.01.org/0day-ci/archive/20260122/202601220042.cudmSYUb-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 15.2.0
smatch version: v0.5.0-8985-g2614ff1a
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260122/202601220042.cudmSYUb-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601220042.cudmSYUb-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ipvlan/ipvlan_main.c:1023:30: warning: 'ipvlan_addr6_vtor_notifier_block' defined but not used [-Wunused-variable]
1023 | static struct notifier_block ipvlan_addr6_vtor_notifier_block __read_mostly = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/ipvlan_addr6_vtor_notifier_block +1023 drivers/net/ipvlan/ipvlan_main.c
8c54904ac0f545 Dmitry Skorodumov 2026-01-20 1022
3ad7d2468f79fc Krister Johansen 2017-06-08 @1023 static struct notifier_block ipvlan_addr6_vtor_notifier_block __read_mostly = {
8c54904ac0f545 Dmitry Skorodumov 2026-01-20 1024 .notifier_call = ipvlan_addr_validator_event_cb,
3ad7d2468f79fc Krister Johansen 2017-06-08 1025 };
8c54904ac0f545 Dmitry Skorodumov 2026-01-20 1026
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-21 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260120161852.639238-1-skorodumov.dmitry@huawei.com>
2026-01-20 16:18 ` [PATCH net 1/3] ipvlan: const-specifier for functions that use iaddr Dmitry Skorodumov
2026-01-20 16:18 ` [PATCH net 2/3] ipvlan: Common code from v6/v4 validator_event Dmitry Skorodumov
2026-01-21 15:33 ` kernel test robot [this message]
2026-01-20 16:18 ` [PATCH net 3/3] ipvlan: common code to handle ipv6/ipv4 address events Dmitry Skorodumov
2026-01-22 3:58 ` kernel test robot
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=202601220042.cudmSYUb-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=dskr99@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shaw.leon@gmail.com \
--cc=skorodumov.dmitry@huawei.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