From: kbuild test robot <lkp@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, davem@davemloft.net,
ganeshgr@chelsio.com, nirranjan@chelsio.com,
indranil@chelsio.com,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Subject: Re: [PATCH net-next 1/2] cxgb4: rework on-chip memory read
Date: Tue, 16 Jan 2018 09:59:27 +0800 [thread overview]
Message-ID: <201801160933.dVCWbUfA%fengguang.wu@intel.com> (raw)
In-Reply-To: <d830e4ed16d2d7da1590d1943030532447bd0366.1515921116.git.rahul.lakkireddy@chelsio.com>
Hi Rahul,
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/Rahul-Lakkireddy/cxgb4-rework-on-chip-memory-read/20180116-050826
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/chelsio/cxgb4/cudbg_intrinsic.c:29:14: sparse: incorrect type in assignment (different base types) @@ expected restricted __be32 <noident> @@ got unsignrestricted __be32 <noident> @@
drivers/net/ethernet/chelsio/cxgb4/cudbg_intrinsic.c:29:14: expected restricted __be32 <noident>
drivers/net/ethernet/chelsio/cxgb4/cudbg_intrinsic.c:29:14: got unsigned int <noident>
vim +29 drivers/net/ethernet/chelsio/cxgb4/cudbg_intrinsic.c
21
22 unsigned int cudbg_mem_read_def(struct cudbg_init *pdbg_init,
23 u32 start, u32 offset, u32 size,
24 u32 mem_aperture, u8 *outbuf)
25 {
26 struct adapter *adap = pdbg_init->adap;
27 __be32 *buf = (__be32 *)outbuf;
28
> 29 *buf = le32_to_cpu((__force __le32)
30 t4_read_reg(adap, start + offset));
31
32 return sizeof(__be32);
33 }
34
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-01-16 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 9:32 [PATCH net-next 0/2] cxgb4: speed up reading on-chip memory Rahul Lakkireddy
2018-01-14 9:32 ` [PATCH net-next 1/2] cxgb4: rework on-chip memory read Rahul Lakkireddy
2018-01-16 1:59 ` kbuild test robot [this message]
2018-01-14 9:32 ` [PATCH net-next 2/2] cxgb4: speed up " Rahul Lakkireddy
2018-01-16 2:56 ` kbuild test robot
2018-01-14 17:17 ` [PATCH net-next 0/2] cxgb4: speed up reading on-chip memory David Miller
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=201801160933.dVCWbUfA%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=indranil@chelsio.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@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;
as well as URLs for NNTP newsgroup(s).