From: kernel test robot <lkp@intel.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: kbuild-all@lists.01.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [pdx86-platform-drivers-x86:platform-drivers-x86-simatec 5/7] drivers/leds/simple/simatic-ipc-leds-gpio.c:18:27: sparse: sparse: symbol 'simatic_ipc_led_gpio_table' was not declared. Should it be static?
Date: Mon, 5 Sep 2022 18:26:45 +0800 [thread overview]
Message-ID: <202209051817.JOPCa9LC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git platform-drivers-x86-simatec
head: 8f5c9858c5db129359b5de2f60f5f034bf5d56c0
commit: a97126265dfe10d3321c0fde4708a6cea49b19ed [5/7] leds: simatic-ipc-leds-gpio: add new model 227G
config: x86_64-randconfig-s022-20220905 (https://download.01.org/0day-ci/archive/20220905/202209051817.JOPCa9LC-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?id=a97126265dfe10d3321c0fde4708a6cea49b19ed
git remote add pdx86-platform-drivers-x86 https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git
git fetch --no-tags pdx86-platform-drivers-x86 platform-drivers-x86-simatec
git checkout a97126265dfe10d3321c0fde4708a6cea49b19ed
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/leds/simple/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/leds/simple/simatic-ipc-leds-gpio.c:18:27: sparse: sparse: symbol 'simatic_ipc_led_gpio_table' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-05 10:27 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=202209051817.JOPCa9LC-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=henning.schild@siemens.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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