From: kernel test robot <lkp@intel.com>
To: Lucas Poupeau <lucasp.linux@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: oe-kbuild-all@lists.linux.dev, horms@kernel.org,
kuniyu@google.com, sdf@fomichev.me, brauner@kernel.org,
krikku@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lucas Poupeau <lucasp.linux@gmail.com>
Subject: Re: [PATCH] net: sysfs: cleanup coding style
Date: Wed, 5 Aug 2026 17:47:12 +0800 [thread overview]
Message-ID: <202608051723.zyzTXXX2-lkp@intel.com> (raw)
In-Reply-To: <20260628185824.231250-1-lucasp.linux@gmail.com>
Hi Lucas,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
[also build test ERROR on net/main brauner-vfs/vfs.all linus/master v7.2-rc6 next-20260804]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lucas-Poupeau/net-sysfs-cleanup-coding-style/20260805-152318
base: net-next/main
patch link: https://lore.kernel.org/r/20260628185824.231250-1-lucasp.linux%40gmail.com
patch subject: [PATCH] net: sysfs: cleanup coding style
config: alpha-allmodconfig (https://download.01.org/0day-ci/archive/20260805/202608051723.zyzTXXX2-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260805/202608051723.zyzTXXX2-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/202608051723.zyzTXXX2-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
In file included from include/linux/dma-mapping.h:5,
from include/linux/skbuff.h:28,
from include/net/net_namespace.h:44,
from include/linux/netdevice.h:38,
from net/core/net-sysfs.c:10:
>> net/core/net-sysfs.c:622:23: error: 'netdev_group_show' undeclared here (not in a function); did you mean 'netdev_show'?
622 | static DEVICE_ATTR_RW(netdev_group);
| ^~~~~~~~~~~~
include/linux/device.h:173:36: note: in definition of macro '__DEVICE_ATTR_SHOW_STORE'
173 | .show = _Generic(_show, \
| ^~~~~
include/linux/device.h:201:9: note: in expansion of macro '__DEVICE_ATTR'
201 | __DEVICE_ATTR(_name, _mode, _name##_show, _name##_store)
| ^~~~~~~~~~~~~
include/linux/device.h:204:9: note: in expansion of macro '__DEVICE_ATTR_RW_MODE'
204 | __DEVICE_ATTR_RW_MODE(_name, 0644)
| ^~~~~~~~~~~~~~~~~~~~~
include/linux/device.h:246:52: note: in expansion of macro '__DEVICE_ATTR_RW'
246 | struct device_attribute dev_attr_##_name = __DEVICE_ATTR_RW(_name)
| ^~~~~~~~~~~~~~~~
net/core/net-sysfs.c:622:8: note: in expansion of macro 'DEVICE_ATTR_RW'
622 | static DEVICE_ATTR_RW(netdev_group);
| ^~~~~~~~~~~~~~
>> net/core/net-sysfs.c:622:23: error: 'netdev_group_store' undeclared here (not in a function); did you mean 'netdev_lock_store'?
622 | static DEVICE_ATTR_RW(netdev_group);
| ^~~~~~~~~~~~
include/linux/device.h:177:36: note: in definition of macro '__DEVICE_ATTR_SHOW_STORE'
177 | .store = _Generic(_store, \
| ^~~~~~
include/linux/device.h:201:9: note: in expansion of macro '__DEVICE_ATTR'
201 | __DEVICE_ATTR(_name, _mode, _name##_show, _name##_store)
| ^~~~~~~~~~~~~
include/linux/device.h:204:9: note: in expansion of macro '__DEVICE_ATTR_RW_MODE'
204 | __DEVICE_ATTR_RW_MODE(_name, 0644)
| ^~~~~~~~~~~~~~~~~~~~~
include/linux/device.h:246:52: note: in expansion of macro '__DEVICE_ATTR_RW'
246 | struct device_attribute dev_attr_##_name = __DEVICE_ATTR_RW(_name)
| ^~~~~~~~~~~~~~~~
net/core/net-sysfs.c:622:8: note: in expansion of macro 'DEVICE_ATTR_RW'
622 | static DEVICE_ATTR_RW(netdev_group);
| ^~~~~~~~~~~~~~
>> net/core/net-sysfs.c:621:16: warning: 'group_show' defined but not used [-Wunused-function]
621 | NETDEVICE_SHOW(group, fmt_dec);
| ^~~~~
net/core/net-sysfs.c:143:16: note: in definition of macro 'NETDEVICE_SHOW'
143 | static ssize_t field##_show(struct device *dev, \
| ^~~~~
>> net/core/net-sysfs.c:615:16: warning: 'group_store' defined but not used [-Wunused-function]
615 | static ssize_t group_store(struct device *dev, struct device_attribute *attr,
| ^~~~~~~~~~~
vim +622 net/core/net-sysfs.c
614
> 615 static ssize_t group_store(struct device *dev, struct device_attribute *attr,
616 const char *buf, size_t len)
617 {
618 return netdev_store(dev, attr, buf, len, change_group);
619 }
620
> 621 NETDEVICE_SHOW(group, fmt_dec);
> 622 static DEVICE_ATTR_RW(netdev_group);
623
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-05 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 18:58 [PATCH] net: sysfs: cleanup coding style Lucas Poupeau
2026-06-28 20:14 ` Andrew Lunn
2026-08-05 9:47 ` kernel test robot [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=202608051723.zyzTXXX2-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krikku@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucasp.linux@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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