From: kernel test robot <lkp@intel.com>
To: Kerem Karabay <kekrby@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-input@vger.kernel.org,
Jiri Kosina <jikos@kernel.org>,
Aditya Garg <gargaditya08@live.com>
Subject: [hid:for-6.15/apple 2/4] drivers/hid/hid-appletb-kbd.c:119:18: sparse: sparse: symbol 'appletb_kbd_attrs' was not declared. Should it be static?
Date: Sun, 9 Feb 2025 11:41:33 +0800 [thread overview]
Message-ID: <202502091105.ZsLoBSIh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-6.15/apple
head: 93a0fc48948107e0cc34e1de22c3cb363a8f2783
commit: 8e9b9152cfbdc2a90a8acb68acbc1407ef67d139 [2/4] HID: hid-appletb-kbd: add driver for the keyboard mode of Apple Touch Bars
config: arc-randconfig-r122-20250209 (https://download.01.org/0day-ci/archive/20250209/202502091105.ZsLoBSIh-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250209/202502091105.ZsLoBSIh-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/202502091105.ZsLoBSIh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/hid/hid-appletb-kbd.c:119:18: sparse: sparse: symbol 'appletb_kbd_attrs' was not declared. Should it be static?
vim +/appletb_kbd_attrs +119 drivers/hid/hid-appletb-kbd.c
118
> 119 struct attribute *appletb_kbd_attrs[] = {
120 &dev_attr_mode.attr,
121 NULL
122 };
123 ATTRIBUTE_GROUPS(appletb_kbd);
124
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-02-09 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 3:41 kernel test robot [this message]
2025-02-09 7:30 ` [hid:for-6.15/apple 2/4] drivers/hid/hid-appletb-kbd.c:119:18: sparse: sparse: symbol 'appletb_kbd_attrs' was not declared. Should it be static? Aditya Garg
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=202502091105.ZsLoBSIh-lkp@intel.com \
--to=lkp@intel.com \
--cc=gargaditya08@live.com \
--cc=jikos@kernel.org \
--cc=kekrby@gmail.com \
--cc=linux-input@vger.kernel.org \
--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