From: kernel test robot <lkp@intel.com>
To: Cedric Xing <cedric.xing@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Dan Williams <dan.j.williams@intel.com>
Subject: [linux-next:master 9587/9729] samples/tsm-mr/tsm_mr_sample.c:17:3: sparse: sparse: symbol 'sample_report' was not declared. Should it be static?
Date: Fri, 9 May 2025 09:38:33 +0800 [thread overview]
Message-ID: <202505090938.avfIhLsl-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f48887a98b78880b7711aca311fbbbcaad6c4e3b
commit: 42ac41dbc5726beff7c0957f15f0a887f70da199 [9587/9729] tsm-mr: Add tsm-mr sample code
config: x86_64-randconfig-r112-20250508 (https://download.01.org/0day-ci/archive/20250509/202505090938.avfIhLsl-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505090938.avfIhLsl-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/202505090938.avfIhLsl-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> samples/tsm-mr/tsm_mr_sample.c:17:3: sparse: sparse: symbol 'sample_report' was not declared. Should it be static?
vim +/sample_report +17 samples/tsm-mr/tsm_mr_sample.c
10
11 struct {
12 u8 static_mr[SHA384_DIGEST_SIZE];
13 u8 config_mr[SHA512_DIGEST_SIZE];
14 u8 rtmr0[SHA256_DIGEST_SIZE];
15 u8 rtmr1[SHA384_DIGEST_SIZE];
16 u8 report_digest[SHA512_DIGEST_SIZE];
> 17 } sample_report = {
18 .static_mr = "static_mr",
19 .config_mr = "config_mr",
20 .rtmr0 = "rtmr0",
21 .rtmr1 = "rtmr1",
22 };
23
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-09 1:39 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=202505090938.avfIhLsl-lkp@intel.com \
--to=lkp@intel.com \
--cc=cedric.xing@intel.com \
--cc=dan.j.williams@intel.com \
--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 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.