From: kernel test robot <lkp@intel.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: [linux-next:master 652/2855] net/netfilter/nf_conntrack_bpf.c:251:5: warning: no previous prototype for 'register_nf_conntrack_bpf'
Date: Sat, 29 Jan 2022 12:33:20 +0800 [thread overview]
Message-ID: <202201291226.CNe1hZ5R-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b605fdc54c2b28c30ef06d9db99282d8a32ae4be
commit: b4c2b9593a1c4c3a718370e34af28e817fd5e5c6 [652/2855] net/netfilter: Add unstable CT lookup helpers for XDP and TC-BPF
config: i386-debian-10.3-kselftests (https://download.01.org/0day-ci/archive/20220129/202201291226.CNe1hZ5R-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b4c2b9593a1c4c3a718370e34af28e817fd5e5c6
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout b4c2b9593a1c4c3a718370e34af28e817fd5e5c6
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> net/netfilter/nf_conntrack_bpf.c:251:5: warning: no previous prototype for 'register_nf_conntrack_bpf' [-Wmissing-prototypes]
251 | int register_nf_conntrack_bpf(void)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/register_nf_conntrack_bpf +251 net/netfilter/nf_conntrack_bpf.c
250
> 251 int register_nf_conntrack_bpf(void)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-29 4:33 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=202201291226.CNe1hZ5R-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=memxor@gmail.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