From: "Takashi Sakamoto" <o-takashi@sakamocchi.jp>
To: "kbuild test robot" <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [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 17:06:42 +0900 [thread overview]
Message-ID: <d44c2848-165f-4412-a8e2-af5d0bfb9691@app.fastmail.com> (raw)
In-Reply-To: <202609060257.8wQo9w9N-lkp@intel.com>
On Sun, Sep 6, 2026, at 03:23, kernel test robot wrote:
> 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
> ...
> 88 u32 *quadlet = payload;
Indeed. This should be typed as __be32. I'll fix it later.
Thanks
Takashi Sakamoto
prev parent reply other threads:[~2026-09-06 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 18:23 [linux-next:master 3200/4370] drivers/firewire/config-rom-parser-test.c:93:18: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2026-09-06 8:06 ` Takashi Sakamoto [this message]
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=d44c2848-165f-4412-a8e2-af5d0bfb9691@app.fastmail.com \
--to=o-takashi@sakamocchi.jp \
--cc=lkp@intel.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.