From: kernel test robot <lkp@intel.com>
To: Alexander Graf <graf@amazon.com>
Cc: oe-kbuild-all@lists.linux.dev, Mike Rapoport <rppt@kernel.org>
Subject: [rppt:kho/v4 12/13] kernel/kexec_handover.c:261:22: sparse: sparse: symbol 'bin_attr_dt_kern' was not declared. Should it be static?
Date: Fri, 7 Feb 2025 12:37:26 +0800 [thread overview]
Message-ID: <202502071211.QXBJTXHa-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git kho/v4
head: c46ab1adade1c0ece83ff5ad4c3aa57ea0126275
commit: bebf0e306ff813f1b55728339a32291d64ca1b69 [12/13] x86: Add KHO support
config: x86_64-randconfig-122-20250207 (https://download.01.org/0day-ci/archive/20250207/202502071211.QXBJTXHa-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250207/202502071211.QXBJTXHa-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/202502071211.QXBJTXHa-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/kexec_handover.c:261:22: sparse: sparse: symbol 'bin_attr_dt_kern' was not declared. Should it be static?
vim +/bin_attr_dt_kern +261 kernel/kexec_handover.c
e990233a3a6935 Alexander Graf 2024-01-17 260
e990233a3a6935 Alexander Graf 2024-01-17 @261 struct bin_attribute bin_attr_dt_kern = __BIN_ATTR(dt, 0400, dt_read, NULL, 0);
e990233a3a6935 Alexander Graf 2024-01-17 262
:::::: The code at line 261 was first introduced by commit
:::::: e990233a3a6935ac84e61a664404855b89def697 kexec: Add Kexec HandOver (KHO) generation helpers
:::::: TO: Alexander Graf <graf@amazon.com>
:::::: CC: Mike Rapoport (Microsoft) <rppt@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-07 4:38 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=202502071211.QXBJTXHa-lkp@intel.com \
--to=lkp@intel.com \
--cc=graf@amazon.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.