[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201803310219.Jgdn8aQo%fengguang.wu@intel.com>
Date: Sat, 31 Mar 2018 03:07:36 +0800
From: kbuild test robot <lkp@...el.com>
To: Jesper Dangaard Brouer <brouer@...hat.com>
Cc: kbuild-all@...org, netdev@...r.kernel.org,
BjörnTöpel <bjorn.topel@...el.com>,
magnus.karlsson@...el.com, eugenia@...lanox.com,
Jason Wang <jasowang@...hat.com>,
John Fastabend <john.fastabend@...il.com>,
Eran Ben Elisha <eranbe@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>, galp@...lanox.com,
Jesper Dangaard Brouer <brouer@...hat.com>,
Daniel Borkmann <borkmann@...earbox.net>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Tariq Toukan <tariqt@...lanox.com>
Subject: Re: [net-next V7 PATCH 11/16] xdp: rhashtable with allocator ID to
pointer mapping
Hi Jesper,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Jesper-Dangaard-Brouer/XDP-redirect-memory-return-API/20180330-203122
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> net/core/xdp.c:19:1: sparse: symbol 'mem_id_pool' was not declared. Should it be static?
>> net/core/xdp.c:68:6: sparse: symbol '__xdp_mem_allocator_rcu_free' was not declared. Should it be static?
>> net/core/xdp.c:87:6: sparse: symbol '__xdp_rxq_info_unreg_mem_model' was not declared. Should it be static?
>> net/core/xdp.c:177:5: sparse: symbol '__mem_id_init_hash_table' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists