From: kernel test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-hwmon@vger.kernel.org
Subject: [groeck-staging:testing 10/11] arch/nios2/kernel/prom.c:24:39: sparse: sparse: incorrect type in initializer (different base types)
Date: Sat, 23 Mar 2024 22:37:43 +0800 [thread overview]
Message-ID: <202403232201.JtbvWJxL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git testing
head: 471566efaf17fc2be0b9be63bf04d2c44fbb3b20
commit: a1f82fe941b07e2ba651fd5ace75e88209adb8ba [10/11] nios2: Only use built-in devicetree blob if configured to do so
config: nios2-randconfig-r132-20240323 (https://download.01.org/0day-ci/archive/20240323/202403232201.JtbvWJxL-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240323/202403232201.JtbvWJxL-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/202403232201.JtbvWJxL-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/nios2/kernel/prom.c:24:39: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted __be32 [usertype] *[unused] dtb @@ got unsigned int [usertype] * @@
arch/nios2/kernel/prom.c:24:39: sparse: expected restricted __be32 [usertype] *[unused] dtb
arch/nios2/kernel/prom.c:24:39: sparse: got unsigned int [usertype] *
vim +24 arch/nios2/kernel/prom.c
21
22 void __init early_init_devtree(void *params)
23 {
> 24 __be32 __maybe_unused *dtb = (u32 *)__dtb_start;
25
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-23 14:38 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=202403232201.JtbvWJxL-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).