From: kernel test robot <lkp@intel.com>
To: yang.guang5@zte.com.cn, davem@davemloft.net
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
jiang.xuexin@zte.com.cn, chen.haonan2@zte.com.cn,
cgel.zte@gmail.com, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, sd@queasysnail.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next] mlxsw: spectrum: use netif_is_macsec() instead of open code
Date: Sun, 17 Dec 2023 20:42:08 +0800 [thread overview]
Message-ID: <202312172042.gMYseKZQ-lkp@intel.com> (raw)
In-Reply-To: <202312152145312776210@zte.com.cn>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20231215]
url: https://github.com/intel-lab-lkp/linux/commits/yang-guang5-zte-com-cn/mlxsw-spectrum-use-netif_is_macsec-instead-of-open-code/20231215-214631
base: next-20231215
patch link: https://lore.kernel.org/r/202312152145312776210%40zte.com.cn
patch subject: [PATCH linux-next] mlxsw: spectrum: use netif_is_macsec() instead of open code
config: i386-buildonly-randconfig-003-20231217 (https://download.01.org/0day-ci/archive/20231217/202312172042.gMYseKZQ-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231217/202312172042.gMYseKZQ-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/202312172042.gMYseKZQ-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from kernel/cgroup/cgroup.c:33:
In file included from include/linux/bpf-cgroup.h:11:
In file included from include/net/sock.h:46:
>> include/linux/netdevice.h:5105:1: warning: all paths through this function will call itself [-Winfinite-recursion]
{
^
1 warning generated.
vim +5105 include/linux/netdevice.h
7967168cefdbc6 Herbert Xu 2006-06-22 5098
14d7b8122fd591 Jakub Kicinski 2022-05-05 5099 void netif_set_tso_max_size(struct net_device *dev, unsigned int size);
14d7b8122fd591 Jakub Kicinski 2022-05-05 5100 void netif_set_tso_max_segs(struct net_device *dev, unsigned int segs);
6df6398f7c8b48 Jakub Kicinski 2022-05-05 5101 void netif_inherit_tso_max(struct net_device *to,
6df6398f7c8b48 Jakub Kicinski 2022-05-05 5102 const struct net_device *from);
6df6398f7c8b48 Jakub Kicinski 2022-05-05 5103
3c17578473b9be Sabrina Dubroca 2016-03-11 5104 static inline bool netif_is_macsec(const struct net_device *dev)
3c17578473b9be Sabrina Dubroca 2016-03-11 @5105 {
55cddeca5e222e Yang Guang 2023-12-15 5106 return netif_is_macsec(dev);
3c17578473b9be Sabrina Dubroca 2016-03-11 5107 }
3c17578473b9be Sabrina Dubroca 2016-03-11 5108
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-12-17 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 13:45 yang.guang5
2023-12-15 14:40 ` Ioana Ciornei
2023-12-17 12:42 ` kernel test robot [this message]
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=202312172042.gMYseKZQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=cgel.zte@gmail.com \
--cc=chen.haonan2@zte.com.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiang.xuexin@zte.com.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=yang.guang5@zte.com.cn \
/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
all inboxes | Powered by JetHome®