From: kernel test robot <lkp@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [l1k:nft_egress_v6 3/6] net/netfilter/core.c:353:20: error: unused function 'nf_egress_hook'
Date: Wed, 13 Oct 2021 09:53:46 +0800 [thread overview]
Message-ID: <202110130939.GGJnWiAD-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
tree: https://github.com/l1k/linux nft_egress_v6
head: c2164307e53a826a4e1a3152e58128561f8ccabd
commit: 700c29bd551c81c325ee11dbc9cf359714add76d [3/6] netfilter: Introduce egress hook
config: hexagon-buildonly-randconfig-r004-20211012 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c3dcf39554dbea780d6cb7e12239451ba47a2668)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/l1k/linux/commit/700c29bd551c81c325ee11dbc9cf359714add76d
git remote add l1k https://github.com/l1k/linux
git fetch --no-tags l1k nft_egress_v6
git checkout 700c29bd551c81c325ee11dbc9cf359714add76d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=hexagon
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
net/netfilter/core.c:344:20: error: unused function 'nf_ingress_hook' [-Werror,-Wunused-function]
static inline bool nf_ingress_hook(const struct nf_hook_ops *reg, int pf)
^
>> net/netfilter/core.c:353:20: error: unused function 'nf_egress_hook' [-Werror,-Wunused-function]
static inline bool nf_egress_hook(const struct nf_hook_ops *reg, int pf)
^
2 errors generated.
vim +/nf_egress_hook +353 net/netfilter/core.c
352
> 353 static inline bool nf_egress_hook(const struct nf_hook_ops *reg, int pf)
354 {
355 return pf == NFPROTO_NETDEV && reg->hooknum == NF_NETDEV_EGRESS;
356 }
357
---
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: 36134 bytes --]
reply other threads:[~2021-10-13 1:54 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=202110130939.GGJnWiAD-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lukas@wunner.de \
--cc=pablo@netfilter.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