From: kernel test robot <lkp@intel.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [sudeep-holla:wip/acpi_ffh_opregion 2/3] drivers/acpi/bus.c:301:6: sparse: sparse: symbol 'osc_sb_ffh_opregion_support_confirmed' was not declared. Should it be static?
Date: Thu, 16 Jun 2022 21:35:37 +0800 [thread overview]
Message-ID: <202206162156.TTEhmMTa-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git wip/acpi_ffh_opregion
head: aca46ad097a20fee2f395f051d575d323c15ffff
commit: 42de507063eebc8c7d728fbac4012e35c8b854df [2/3] ACPI: Implement a generic FFH Opregion handler
config: i386-randconfig-s001 (https://download.01.org/0day-ci/archive/20220616/202206162156.TTEhmMTa-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-30-g92122700-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/commit/?id=42de507063eebc8c7d728fbac4012e35c8b854df
git remote add sudeep-holla https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git
git fetch --no-tags sudeep-holla wip/acpi_ffh_opregion
git checkout 42de507063eebc8c7d728fbac4012e35c8b854df
# 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=i386 SHELL=/bin/bash drivers/acpi/
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/acpi/bus.c:301:6: sparse: sparse: symbol 'osc_sb_ffh_opregion_support_confirmed' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-16 13:36 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=202206162156.TTEhmMTa-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.com \
/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
Powered by JetHome