From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-6.1 0/1] drivers/firmware/arm_scmi/shmem.c:190:9: warning: 'reg_io_width' is used uninitialized
Date: Tue, 28 Jul 2026 18:42:10 +0800 [thread overview]
Message-ID: <202607281819.jg2NEySd-lkp@intel.com> (raw)
Hi Florian,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android14-6.1
head: a6fc30b246f0d8be1c91e0d37c8b3bc859b1b2bc
commit: fa34bcaf9e7b5bd86a417a14ea86bb88d9ea524e [0/1] BACKPORT: firmware: arm_scmi: Support 'reg-io-width' property for shared memory
config: x86_64-buildonly-randconfig-003-20260728 (https://download.01.org/0day-ci/archive/20260728/202607281819.jg2NEySd-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260728/202607281819.jg2NEySd-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/202607281819.jg2NEySd-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/firmware/arm_scmi/shmem.c: In function 'shmem_get_io_ops':
>> drivers/firmware/arm_scmi/shmem.c:190:9: warning: 'reg_io_width' is used uninitialized [-Wuninitialized]
190 | switch (reg_io_width) {
| ^~~~~~
drivers/firmware/arm_scmi/shmem.c:187:13: note: 'reg_io_width' was declared here
187 | u32 reg_io_width;
| ^~~~~~~~~~~~
vim +/reg_io_width +190 drivers/firmware/arm_scmi/shmem.c
184
185 struct scmi_shmem_io_ops *shmem_get_io_ops(struct device_node *shmem)
186 {
187 u32 reg_io_width;
188
189 of_property_read_u32(shmem, "reg-io-width", ®_io_width);
> 190 switch (reg_io_width) {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-28 10:42 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=202607281819.jg2NEySd-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.