From: kernel test robot <lkp@intel.com>
To: yangge1116@126.com, ardb@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, jarkko@kernel.org,
sathyanarayanan.kuppuswamy@linux.intel.com,
ilias.apalodimas@linaro.org, jgg@ziepe.ca,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, liuzixing@hygon.cn,
Ge Yang <yangge1116@126.com>
Subject: Re: [PATCH V2] efi/tpm: Fix the issue where the CC platforms event log header can't be correctly identified
Date: Sun, 6 Jul 2025 00:51:34 +0800 [thread overview]
Message-ID: <202507060016.n5ikMP6Q-lkp@intel.com> (raw)
In-Reply-To: <1751710616-24464-1-git-send-email-yangge1116@126.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on efi/next]
[also build test ERROR on char-misc/char-misc-testing char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.16-rc4 next-20250704]
[cannot apply to intel-tdx/guest-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/yangge1116-126-com/efi-tpm-Fix-the-issue-where-the-CC-platforms-event-log-header-can-t-be-correctly-identified/20250705-182032
base: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
patch link: https://lore.kernel.org/r/1751710616-24464-1-git-send-email-yangge1116%40126.com
patch subject: [PATCH V2] efi/tpm: Fix the issue where the CC platforms event log header can't be correctly identified
config: arc-randconfig-002-20250705 (https://download.01.org/0day-ci/archive/20250706/202507060016.n5ikMP6Q-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250706/202507060016.n5ikMP6Q-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/202507060016.n5ikMP6Q-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
drivers/char/tpm/eventlog/tpm2.c: In function 'calc_tpm2_event_size':
>> drivers/char/tpm/eventlog/tpm2.c:40:25: error: implicit declaration of function 'cc_platform_has' [-Werror=implicit-function-declaration]
40 | cc_platform_has(CC_ATTR_GUEST_STATE_ENCRYPT));
| ^~~~~~~~~~~~~~~
>> drivers/char/tpm/eventlog/tpm2.c:40:41: error: 'CC_ATTR_GUEST_STATE_ENCRYPT' undeclared (first use in this function)
40 | cc_platform_has(CC_ATTR_GUEST_STATE_ENCRYPT));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/char/tpm/eventlog/tpm2.c:40:41: note: each undeclared identifier is reported only once for each function it appears in
>> drivers/char/tpm/eventlog/tpm2.c:41:1: warning: control reaches end of non-void function [-Wreturn-type]
41 | }
| ^
cc1: some warnings being treated as errors
vim +/cc_platform_has +40 drivers/char/tpm/eventlog/tpm2.c
24
25 /*
26 * calc_tpm2_event_size() - calculate the event size, where event
27 * is an entry in the TPM 2.0 event log. The event is of type Crypto
28 * Agile Log Entry Format as defined in TCG EFI Protocol Specification
29 * Family "2.0".
30
31 * @event: event whose size is to be calculated.
32 * @event_header: the first event in the event log.
33 *
34 * Returns size of the event. If it is an invalid event, returns 0.
35 */
36 static size_t calc_tpm2_event_size(struct tcg_pcr_event2_head *event,
37 struct tcg_pcr_event *event_header)
38 {
39 return __calc_tpm2_event_size(event, event_header, false,
> 40 cc_platform_has(CC_ATTR_GUEST_STATE_ENCRYPT));
> 41 }
42
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-05 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 10:16 [PATCH V2] efi/tpm: Fix the issue where the CC platforms event log header can't be correctly identified yangge1116
2025-07-05 16:51 ` kernel test robot [this message]
2025-07-19 12:36 ` Jarkko Sakkinen
2025-07-21 0:45 ` Ge Yang
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=202507060016.n5ikMP6Q-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzixing@hygon.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=yangge1116@126.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