mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Xue Chaojing <xuechaojing@huawei.com>
Cc: kbuild-all@01.org, davem@davemloft.net,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	luoshaokai@huawei.com, cloud.wangxiaoyun@huawei.com,
	xuechaojing@huawei.com, chiqijun@huawei.com, wulike1@huawei.com
Subject: Re: [PATCH net-next v3] hinic: add LRO support
Date: Tue, 4 Jun 2019 07:23:10 +0800	[thread overview]
Message-ID: <201906040753.bqwbqtxT%lkp@intel.com> (raw)
In-Reply-To: <20190603043536.4970-1-xuechaojing@huawei.com>

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@intel.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

  parent reply	other threads:[~2019-06-03 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  4:35 Xue Chaojing
2019-06-03 23:05 ` Jesse Brandeburg
2019-06-04  9:02   ` xuechaojing
2019-06-03 23:23 ` kbuild test robot [this message]
2019-06-03 23:23 ` [RFC PATCH] hinic: hinic_rx_configure() can be static kbuild test robot

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=201906040753.bqwbqtxT%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chiqijun@huawei.com \
    --cc=cloud.wangxiaoyun@huawei.com \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luoshaokai@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=wulike1@huawei.com \
    --cc=xuechaojing@huawei.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

Powered by JetHome