From: kbuild test robot <lkp@intel.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: kbuild-all@lists.01.org,
linux-kernel <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86: Optimise x86 IP checksum code
Date: Fri, 6 Dec 2019 09:45:01 +0800 [thread overview]
Message-ID: <201912060941.f3Qi9xtV%lkp@intel.com> (raw)
In-Reply-To: <c92db041c78e4d81a70aaf4249393901@AcuMS.aculab.com>
Hi David,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/auto-latest]
[also build test WARNING on tip/x86/core linus/master v5.4 next-20191202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/David-Laight/x86-Optimise-x86-IP-checksum-code/20191203-211313
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git e445033e58108a9891abfbc0dea90b066a75e4a9
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-91-g817270f-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 >>)
>> arch/x86/lib/csum-partial_64.c:141:23: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __wsum @@ got icted __wsum @@
>> arch/x86/lib/csum-partial_64.c:141:23: sparse: expected restricted __wsum
>> arch/x86/lib/csum-partial_64.c:141:23: sparse: got unsigned int
vim +141 arch/x86/lib/csum-partial_64.c
126
127 /*
128 * computes the checksum of a memory block at buff, length len,
129 * and adds in "sum" (32-bit)
130 *
131 * returns a 32-bit number suitable for feeding into itself
132 * or csum_tcpudp_magic
133 *
134 * this function must be called with even lengths, except
135 * for the last fragment, which may be odd
136 *
137 * it's best to have buff aligned on a 64-bit boundary
138 */
139 __wsum csum_partial(const void *buff, int len, __wsum sum)
140 {
> 141 return do_csum(buff, len, (__force u32)sum);
142 }
143 EXPORT_SYMBOL(csum_partial);
144
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
next prev parent reply other threads:[~2019-12-06 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 11:52 [PATCH] x86: Optimise x86 IP checksum code David Laight
2019-12-04 9:14 ` Peter Zijlstra
2019-12-04 10:06 ` David Laight
2019-12-06 1:45 ` kbuild test robot [this message]
2019-12-09 17:12 ` David Laight
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=201912060941.f3Qi9xtV%lkp@intel.com \
--to=lkp@intel.com \
--cc=David.Laight@ACULAB.COM \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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