From: kbuild test robot <lkp@intel.com>
To: Vishal Kulkarni <vishal@chelsio.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, davem@davemloft.net,
nirranjan@chelsio.com, indranil@chelsio.com, dt@chelsio.com,
Vishal Kulkarni <vishal@chelsio.com>
Subject: Re: [PATCH net-next] cxgb4: Enable hash filter with offload
Date: Tue, 21 May 2019 19:01:12 +0800 [thread overview]
Message-ID: <201905211845.3ECR6kq7%lkp@intel.com> (raw)
In-Reply-To: <1558410037-29161-1-git-send-email-vishal@chelsio.com>
Hi Vishal,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Vishal-Kulkarni/cxgb4-Enable-hash-filter-with-offload/20190521-171528
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/chelsio/cxgb4/t4_hw.c:6216:14: sparse: sparse: symbol 't4_get_tp_e2c_map' was not declared. Should it be static?
drivers/net/ethernet/chelsio/cxgb4/t4_hw.c:3838:9: sparse: sparse: context imbalance in 't4_load_phy_fw' - different lock contexts for basic block
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
next prev parent reply other threads:[~2019-05-21 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 3:40 [PATCH net-next] cxgb4: Enable hash filter with offload Vishal Kulkarni
2019-05-21 11:01 ` kbuild test robot [this message]
2019-05-21 11:01 ` [RFC PATCH] cxgb4: t4_get_tp_e2c_map() can be static kbuild test robot
2019-05-21 20:24 ` [PATCH net-next] cxgb4: Enable hash filter with offload David Miller
2019-05-22 15:00 ` Vishal Kulkarni
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=201905211845.3ECR6kq7%lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=dt@chelsio.com \
--cc=indranil@chelsio.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=vishal@chelsio.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