From: kernel test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next 3/4] ipmr: use exit_batch_rtnl method
Date: Fri, 9 Feb 2024 20:26:00 +0800 [thread overview]
Message-ID: <202402092023.Upwn6RGF-lkp@intel.com> (raw)
In-Reply-To: <20240208111646.535705-4-edumazet@google.com>
Hi Eric,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Eric-Dumazet/ip6mr-use-exit_batch_rtnl-method/20240208-192057
base: net-next/main
patch link: https://lore.kernel.org/r/20240208111646.535705-4-edumazet%40google.com
patch subject: [PATCH net-next 3/4] ipmr: use exit_batch_rtnl method
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240209/202402092023.Upwn6RGF-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240209/202402092023.Upwn6RGF-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/202402092023.Upwn6RGF-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/ipv4/ipmr.c:3134:16: error: incompatible function pointer types initializing 'void (*)(struct list_head *)' with an expression of type 'void (struct list_head *, struct list_head *)' [-Wincompatible-function-pointer-types]
3134 | .exit_batch = ipmr_exit_batch_rtnl,
| ^~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +3134 net/ipv4/ipmr.c
3130
3131 static struct pernet_operations ipmr_net_ops = {
3132 .init = ipmr_net_init,
3133 .exit = ipmr_net_exit,
> 3134 .exit_batch = ipmr_exit_batch_rtnl,
3135 };
3136
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-09 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 11:16 [PATCH net-next 0/4] inet: convert to exit_batch_rtnl Eric Dumazet
2024-02-08 11:16 ` [PATCH net-next 1/4] ip6mr: use exit_batch_rtnl method Eric Dumazet
2024-02-08 11:16 ` [PATCH net-next 2/4] ipv6: fib6: " Eric Dumazet
2024-02-08 11:16 ` [PATCH net-next 3/4] ipmr: " Eric Dumazet
2024-02-08 11:53 ` Eric Dumazet
2024-02-09 8:01 ` kernel test robot
2024-02-09 12:26 ` kernel test robot [this message]
2024-02-08 11:16 ` [PATCH net-next 4/4] ipv4: fib: " Eric Dumazet
2024-02-08 17:54 ` [PATCH net-next 0/4] inet: convert to exit_batch_rtnl Eric Dumazet
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=202402092023.Upwn6RGF-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).