From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>
Subject: arch/nios2/include/asm/checksum.h:30:24: sparse: sparse: restricted __wsum degrades to integer
Date: Thu, 11 Jun 2026 18:50:02 +0800 [thread overview]
Message-ID: <202606111818.O5tEL43L-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9716c086c8e8b141d35aa61f2e96a2e83de212a7
commit: 203247c5cb972af5d46bdb7d41ef40078048810b blk-integrity: support arbitrary buffer alignment
date: 3 months ago
config: nios2-randconfig-r134-20260611 (https://download.01.org/0day-ci/archive/20260611/202606111818.O5tEL43L-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260611/202606111818.O5tEL43L-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Fixes: 203247c5cb97 ("blk-integrity: support arbitrary buffer alignment")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606111818.O5tEL43L-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
block/t10-pi.c: note: in included file (through include/net/checksum.h):
>> arch/nios2/include/asm/checksum.h:30:24: sparse: sparse: restricted __wsum degrades to integer
vim +30 arch/nios2/include/asm/checksum.h
eea9507a69d637d Ley Foon Tan 2014-11-06 17
eea9507a69d637d Ley Foon Tan 2014-11-06 18 /*
eea9507a69d637d Ley Foon Tan 2014-11-06 19 * Fold a partial checksum
eea9507a69d637d Ley Foon Tan 2014-11-06 20 */
eea9507a69d637d Ley Foon Tan 2014-11-06 21 static inline __sum16 csum_fold(__wsum sum)
eea9507a69d637d Ley Foon Tan 2014-11-06 22 {
eea9507a69d637d Ley Foon Tan 2014-11-06 23 __asm__ __volatile__(
eea9507a69d637d Ley Foon Tan 2014-11-06 24 "add %0, %1, %0\n"
eea9507a69d637d Ley Foon Tan 2014-11-06 25 "cmpltu r8, %0, %1\n"
eea9507a69d637d Ley Foon Tan 2014-11-06 26 "srli %0, %0, 16\n"
eea9507a69d637d Ley Foon Tan 2014-11-06 27 "add %0, %0, r8\n"
eea9507a69d637d Ley Foon Tan 2014-11-06 28 "nor %0, %0, %0\n"
eea9507a69d637d Ley Foon Tan 2014-11-06 29 : "=r" (sum)
eea9507a69d637d Ley Foon Tan 2014-11-06 @30 : "r" (sum << 16), "0" (sum)
eea9507a69d637d Ley Foon Tan 2014-11-06 31 : "r8");
eea9507a69d637d Ley Foon Tan 2014-11-06 32 return (__force __sum16) sum;
eea9507a69d637d Ley Foon Tan 2014-11-06 33 }
eea9507a69d637d Ley Foon Tan 2014-11-06 34
:::::: The code at line 30 was first introduced by commit
:::::: eea9507a69d637d52705de8703b168bf6bfe5643 nios2: Library functions
:::::: TO: Ley Foon Tan <lftan@altera.com>
:::::: CC: Ley Foon Tan <lftan@altera.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-06-11 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 10:50 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 14:15 kernel 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=202606111818.O5tEL43L-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®