From: kernel test robot <lkp@intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org,
"Thomas Weißschuh " <thomas.weissschuh@linutronix.de>
Subject: [brgl:gpio/for-next 20/30] drivers/gpio/gpio-virtuser.c:1603:10: error: 'const struct config_item_type' has no member named 'ct_attrs_const'
Date: Wed, 28 Oct 2026 13:51:14 +0100 [thread overview]
Message-ID: <202610281320.OShGuP6l-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
head: 5e826d71d4839d8471784d968274823f1f492eb5
commit: a67ab3994716e1bfe86b53330d1cf2f5bf6bfbad [20/30] gpio: virtuser: constify struct configfs_attribute
config: openrisc-randconfig-r2200-20261028 (https://download.01.org/0day-ci/archive/20261028/202610281320.OShGuP6l-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 16.2.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261028/202610281320.OShGuP6l-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/202610281320.OShGuP6l-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpio/gpio-virtuser.c:1603:10: error: 'const struct config_item_type' has no member named 'ct_attrs_const'
1603 | .ct_attrs_const = gpio_virtuser_lookup_entry_config_attrs,
| ^~~~~~~~~~~~~~
>> drivers/gpio/gpio-virtuser.c:1603:27: error: initialization of 'const struct configfs_group_operations *' from incompatible pointer type 'const struct configfs_attribute * const*' [-Wincompatible-pointer-types]
1603 | .ct_attrs_const = gpio_virtuser_lookup_entry_config_attrs,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpio/gpio-virtuser.c:1603:27: note: (near initialization for 'gpio_virtuser_lookup_entry_config_group_type.ct_group_ops')
drivers/gpio/gpio-virtuser.c:1719:10: error: 'const struct config_item_type' has no member named 'ct_attrs_const'
1719 | .ct_attrs_const = gpio_virtuser_device_config_attrs,
| ^~~~~~~~~~~~~~
drivers/gpio/gpio-virtuser.c:1719:27: error: initialization of 'const struct configfs_group_operations *' from incompatible pointer type 'const struct configfs_attribute * const*' [-Wincompatible-pointer-types]
1719 | .ct_attrs_const = gpio_virtuser_device_config_attrs,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpio/gpio-virtuser.c:1719:27: note: (near initialization for 'gpio_virtuser_device_config_group_type.ct_group_ops')
drivers/gpio/gpio-virtuser.c:1719:27: warning: initialized field overwritten [-Woverride-init]
drivers/gpio/gpio-virtuser.c:1719:27: note: (near initialization for 'gpio_virtuser_device_config_group_type.ct_group_ops')
vim +1603 drivers/gpio/gpio-virtuser.c
1599
1600 static const struct
1601 config_item_type gpio_virtuser_lookup_entry_config_group_type = {
1602 .ct_item_ops = &gpio_virtuser_lookup_entry_config_item_ops,
> 1603 .ct_attrs_const = gpio_virtuser_lookup_entry_config_attrs,
1604 .ct_owner = THIS_MODULE,
1605 };
1606
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-28 12:51 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=202610281320.OShGuP6l-lkp@intel.com \
--to=lkp@intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=linux-gpio@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
/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