The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: drivers/mtd/nand/raw/nand_legacy.c:42:17: sparse: sparse: cast from restricted __le16
Date: Fri, 12 Dec 2025 13:21:57 +0800	[thread overview]
Message-ID: <202512121344.mk9pws1F-lkp@intel.com> (raw)

Hi Matthias,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   d358e5254674b70f34c847715ca509e46eb81e6f
commit: 2abb6e53b5b08987265946b258ca29762091930c gpio: tqmx86: use cleanup guards for spinlock
date:   12 months ago
config: x86_64-randconfig-121-20251212 (https://download.01.org/0day-ci/archive/20251212/202512121344.mk9pws1F-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251212/202512121344.mk9pws1F-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/202512121344.mk9pws1F-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/mtd/nand/raw/nand_legacy.c:42:17: sparse: sparse: cast from restricted __le16

vim +42 drivers/mtd/nand/raw/nand_legacy.c

3d4af7c195850c Boris Brezillon 2018-09-07  32  
3d4af7c195850c Boris Brezillon 2018-09-07  33  /**
3d4af7c195850c Boris Brezillon 2018-09-07  34   * nand_read_byte16 - [DEFAULT] read one byte endianness aware from the chip
3d4af7c195850c Boris Brezillon 2018-09-07  35   * @chip: NAND chip object
3d4af7c195850c Boris Brezillon 2018-09-07  36   *
3d4af7c195850c Boris Brezillon 2018-09-07  37   * Default read function for 16bit buswidth with endianness conversion.
3d4af7c195850c Boris Brezillon 2018-09-07  38   *
3d4af7c195850c Boris Brezillon 2018-09-07  39   */
3d4af7c195850c Boris Brezillon 2018-09-07  40  static uint8_t nand_read_byte16(struct nand_chip *chip)
3d4af7c195850c Boris Brezillon 2018-09-07  41  {
3d4af7c195850c Boris Brezillon 2018-09-07 @42  	return (uint8_t) cpu_to_le16(readw(chip->legacy.IO_ADDR_R));
3d4af7c195850c Boris Brezillon 2018-09-07  43  }
3d4af7c195850c Boris Brezillon 2018-09-07  44  

:::::: The code at line 42 was first introduced by commit
:::::: 3d4af7c195850cfccaddc2cf03b010b95236b695 mtd: rawnand: Move legacy code to nand_legacy.c

:::::: TO: Boris Brezillon <boris.brezillon@bootlin.com>
:::::: CC: Miquel Raynal <miquel.raynal@bootlin.com>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2025-12-12  5:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12  5:21 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-05  6:02 drivers/mtd/nand/raw/nand_legacy.c:42:17: sparse: sparse: cast from restricted __le16 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=202512121344.mk9pws1F-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.schiffer@ew.tq-group.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