All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 3200/4370] drivers/firewire/config-rom-parser-test.c:93:18: sparse: sparse: incorrect type in assignment (different base types)
Date: Sun, 06 Sep 2026 02:23:41 +0800	[thread overview]
Message-ID: <202609060257.8wQo9w9N-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   af5f12805e5cefa4fe68d6127c7e1fb78cd5535c
commit: 23e0d2e849eb84b8451c3f90e660222eea20f031 [3200/4370] firewire: core: add test to detect irm-is-1394-1995-only quirk in config ROM parser
config: csky-randconfig-r113-20260905 (https://download.01.org/0day-ci/archive/20260906/202609060257.8wQo9w9N-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 12.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260906/202609060257.8wQo9w9N-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/202609060257.8wQo9w9N-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   drivers/firewire/core-device.c: note: in included file:
>> drivers/firewire/config-rom-parser-test.c:93:18: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] @@     got restricted __be32 [usertype] @@
   drivers/firewire/config-rom-parser-test.c:93:18: sparse:     expected unsigned int [usertype]
   drivers/firewire/config-rom-parser-test.c:93:18: sparse:     got restricted __be32 [usertype]

vim +93 drivers/firewire/config-rom-parser-test.c

    74	
    75	static int stub_run_regular_transaction(struct fw_card *card, int tcode, int destination_id,
    76						int generation, int speed, unsigned long long offset,
    77						void *payload, size_t length)
    78	{
    79		struct kunit *test = kunit_get_current_test();
    80		const struct parser_test_case *param = test->param_value;
    81	
    82		KUNIT_ASSERT_GE(test, offset, CSR_REGISTER_BASE | CSR_CONFIG_ROM);
    83		KUNIT_ASSERT_LT(test, offset, CSR_REGISTER_BASE | CSR_CONFIG_ROM_END);
    84		KUNIT_ASSERT_NOT_NULL(test, payload);
    85		KUNIT_ASSERT_EQ(test, length, 4);
    86	
    87		unsigned int index = (offset - (CSR_REGISTER_BASE | CSR_CONFIG_ROM)) / sizeof(u32);
    88		u32 *quadlet = payload;
    89	
    90		KUNIT_EXPECT_LE(test, speed, param->expected_speed);
    91		KUNIT_EXPECT_LT(test, index, param->quadlet_length);
    92	
  > 93		*quadlet = cpu_to_be32(param->quadlets[index]);
    94	
    95		return RCODE_COMPLETE;
    96	}
    97	

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

             reply	other threads:[~2026-09-05 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 18:23 kernel test robot [this message]
2026-09-06  8:06 ` [linux-next:master 3200/4370] drivers/firewire/config-rom-parser-test.c:93:18: sparse: sparse: incorrect type in assignment (different base types) Takashi Sakamoto

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=202609060257.8wQo9w9N-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=o-takashi@sakamocchi.jp \
    --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.