Linux M68K Architecture development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Greg Ungerer <gerg@uclinux.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-m68k@lists.linux-m68k.org,
	uclinux-dev@uclinux.org
Subject: [gerg-m68knommu:armnommu 3/3] drivers/mtd/maps/physmap-ixp4xx.c:47:9: sparse: sparse: incorrect type in assignment (different base types)
Date: Tue, 19 May 2026 20:13:08 +0800	[thread overview]
Message-ID: <202605192043.FdeJc20I-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git armnommu
head:   b9d1c6c54795dbb93bb9f68f60a4da071e2ad418
commit: b9d1c6c54795dbb93bb9f68f60a4da071e2ad418 [3/3] ARM: versatile: support configuring versatile machine for no-MMU
config: arm-randconfig-r133-20260519 (https://download.01.org/0day-ci/archive/20260519/202605192043.FdeJc20I-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260519/202605192043.FdeJc20I-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/202605192043.FdeJc20I-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   drivers/mtd/maps/physmap-ixp4xx.c:42:16: sparse: sparse: cast to restricted __be16
   drivers/mtd/maps/physmap-ixp4xx.c:42:16: sparse: sparse: cast to restricted __be16
   drivers/mtd/maps/physmap-ixp4xx.c:42:16: sparse: sparse: cast to restricted __be16
   drivers/mtd/maps/physmap-ixp4xx.c:42:16: sparse: sparse: cast to restricted __be16
>> drivers/mtd/maps/physmap-ixp4xx.c:47:9: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned short volatile @@     got restricted __be16 [usertype] @@
   drivers/mtd/maps/physmap-ixp4xx.c:47:9: sparse:     expected unsigned short volatile
   drivers/mtd/maps/physmap-ixp4xx.c:47:9: sparse:     got restricted __be16 [usertype]

vim +47 drivers/mtd/maps/physmap-ixp4xx.c

2aba2f2a704d368 Linus Walleij 2019-10-21  39  
2aba2f2a704d368 Linus Walleij 2019-10-21  40  static inline u16 flash_read16(void __iomem *addr)
2aba2f2a704d368 Linus Walleij 2019-10-21  41  {
2aba2f2a704d368 Linus Walleij 2019-10-21 @42  	return be16_to_cpu(__raw_readw((void __iomem *)((unsigned long)addr ^ 0x2)));
2aba2f2a704d368 Linus Walleij 2019-10-21  43  }
2aba2f2a704d368 Linus Walleij 2019-10-21  44  
2aba2f2a704d368 Linus Walleij 2019-10-21  45  static inline void flash_write16(u16 d, void __iomem *addr)
2aba2f2a704d368 Linus Walleij 2019-10-21  46  {
2aba2f2a704d368 Linus Walleij 2019-10-21 @47  	__raw_writew(cpu_to_be16(d), (void __iomem *)((unsigned long)addr ^ 0x2));
2aba2f2a704d368 Linus Walleij 2019-10-21  48  }
2aba2f2a704d368 Linus Walleij 2019-10-21  49  

:::::: The code at line 47 was first introduced by commit
:::::: 2aba2f2a704d368583e832555b25d88265e62b6d mtd: physmap_of: add a hook for Intel IXP4xx flash probing

:::::: TO: Linus Walleij <linus.walleij@linaro.org>
:::::: CC: Miquel Raynal <miquel.raynal@bootlin.com>

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

                 reply	other threads:[~2026-05-19 12:15 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=202605192043.FdeJc20I-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=uclinux-dev@uclinux.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