From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Yue Haibing <yuehaibing@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 29971/30000] drivers/net/ipvlan/ipvlan_main.c:431:19: warning: variable 'old_prog' set but not used
Date: Fri, 11 Oct 2024 19:03:54 +0800 [thread overview]
Message-ID: <202410111924.i3Aw2F5F-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: 33a5644b70e15c265ec94eb3726216950a1476ef
commit: 373ce97bdbb6378acf984656798aff4bb706a447 [29971/30000] ipvlan: support use xdp native mode
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241011/202410111924.i3Aw2F5F-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241011/202410111924.i3Aw2F5F-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/202410111924.i3Aw2F5F-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ipvlan/ipvlan_main.c:431:19: warning: variable 'old_prog' set but not used [-Wunused-but-set-variable]
431 | struct bpf_prog *old_prog;
| ^
1 warning generated.
vim +/old_prog +431 drivers/net/ipvlan/ipvlan_main.c
426
427 static int ipvlan_xdp_set(struct net_device *dev, struct bpf_prog *prog,
428 struct netlink_ext_ack *extack)
429 {
430 struct ipvl_dev *priv = netdev_priv(dev);
> 431 struct bpf_prog *old_prog;
432
433 old_prog = rtnl_dereference(priv->xdp_prog);
434 rcu_assign_pointer(priv->xdp_prog, prog);
435 return 0;
436 }
437
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-11 11:04 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=202410111924.i3Aw2F5F-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yuehaibing@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.