[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201906040753.bqwbqtxT%lkp@intel.com>
Date: Tue, 4 Jun 2019 07:23:10 +0800
From: kbuild test robot <lkp@...el.com>
To: Xue Chaojing <xuechaojing@...wei.com>
Cc: kbuild-all@...org, davem@...emloft.net,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
luoshaokai@...wei.com, cloud.wangxiaoyun@...wei.com,
xuechaojing@...wei.com, chiqijun@...wei.com, wulike1@...wei.com
Subject: Re: [PATCH net-next v3] hinic: add LRO support
Hi Xue,
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/Xue-Chaojing/hinic-add-LRO-support/20190604-035042
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@...el.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/huawei/hinic/hinic_main.c:375:5: sparse: sparse: symbol 'hinic_rx_configure' was not declared. Should it be static?
--
>> drivers/net/ethernet/huawei/hinic/hinic_port.c:469:5: sparse: sparse: symbol 'hinic_set_rx_lro' was not declared. Should it be static?
>> drivers/net/ethernet/huawei/hinic/hinic_port.c:497:5: sparse: sparse: symbol 'hinic_set_rx_lro_timer' 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