From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:bcachefs-testing 320/388] fs/bcachefs/sb-errors.c:62:17: sparse: sparse: restricted __le64 degrades to integer
Date: Tue, 9 Sep 2025 09:52:19 +0800 [thread overview]
Message-ID: <202509090923.26KdFSVG-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs bcachefs-testing
head: fe7eb7dac39e94bb0542dfcd5ff88ad3af9be3a7
commit: aa8c3edd73b9e5a2d9134211fb47a74bf68e2b32 [320/388] bcachefs: Print sb_field_errors sorted by datetime
config: hexagon-randconfig-r113-20250909 (https://download.01.org/0day-ci/archive/20250909/202509090923.26KdFSVG-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 7fb1dc08d2f025aad5777bb779dfac1197e9ef87)
reproduce: (https://download.01.org/0day-ci/archive/20250909/202509090923.26KdFSVG-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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509090923.26KdFSVG-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/bcachefs/sb-errors.c:62:17: sparse: sparse: restricted __le64 degrades to integer
>> fs/bcachefs/sb-errors.c:62:17: sparse: sparse: restricted __le64 degrades to integer
>> fs/bcachefs/sb-errors.c:62:17: sparse: sparse: restricted __le64 degrades to integer
>> fs/bcachefs/sb-errors.c:62:17: sparse: sparse: restricted __le64 degrades to integer
vim +62 fs/bcachefs/sb-errors.c
56
57 static int error_entry_cmp(const void *_l, const void *_r)
58 {
59 const struct bch_sb_field_error_entry *l = _l;
60 const struct bch_sb_field_error_entry *r = _r;
61
> 62 return -cmp_int(l->last_error_time, r->last_error_time);
63 }
64
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-09 1:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202509090923.26KdFSVG-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.