From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-kminext 0/1] drivers/misc/eeprom/m24lr.c:346:24: sparse: sparse: cast to restricted __le32
Date: Fri, 06 Nov 2026 01:36:52 +0100 [thread overview]
Message-ID: <202611060150.ba9d5Xcf-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18-kminext
head: a9580b7485bbf58d7b44b7d51e15c8ebe1cea327
commit: cd5c5e0231c538a5d2d4a73f3b3ffc77ff08449c [0/1] eeprom: add driver for ST M24LR series RFID/NFC EEPROM chips
config: i386-randconfig-2300-20261105 (https://download.01.org/0day-ci/archive/20261106/202611060150.ba9d5Xcf-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261106/202611060150.ba9d5Xcf-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: cd5c5e0231c5 ("eeprom: add driver for ST M24LR series RFID/NFC EEPROM chips")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202611060150.ba9d5Xcf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/misc/eeprom/m24lr.c:343:24: sparse: sparse: cast to restricted __le16
drivers/misc/eeprom/m24lr.c:343:24: sparse: sparse: cast from restricted __le64
>> drivers/misc/eeprom/m24lr.c:346:24: sparse: sparse: cast to restricted __le32
drivers/misc/eeprom/m24lr.c:346:24: sparse: sparse: cast from restricted __le64
vim +346 drivers/misc/eeprom/m24lr.c
323
324 static ssize_t m24lr_read_reg_le(struct m24lr *m24lr, u64 *val,
325 unsigned int reg_addr,
326 unsigned int reg_size)
327 {
328 ssize_t ret;
329 __le64 input = 0;
330
331 ret = m24lr_read(m24lr, (u8 *)&input, reg_size, reg_addr, false);
332 if (IS_ERR_VALUE(ret))
333 return ret;
334
335 if (ret != reg_size)
336 return -EINVAL;
337
338 switch (reg_size) {
339 case 1:
340 *val = *(u8 *)&input;
341 break;
342 case 2:
343 *val = le16_to_cpu((__le16)input);
344 break;
345 case 4:
> 346 *val = le32_to_cpu((__le32)input);
347 break;
348 case 8:
349 *val = le64_to_cpu((__le64)input);
350 break;
351 default:
352 return -EINVAL;
353 };
354
355 return 0;
356 }
357
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-06 0:37 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=202611060150.ba9d5Xcf-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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 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.