From: kernel test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [intel-tdx:guest-tpm 5/6] drivers/char/tpm/tpm_tdx.c:175: warning: Function parameter or struct member 'tdvmcall_status' not described in 'tdx_tpm_msg_resp'
Date: Sat, 27 Jan 2024 01:58:38 +0800 [thread overview]
Message-ID: <202401270147.6zANIFto-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git guest-tpm
head: 479fce1c3eaa87d98d94d78c485d9a6f0c8dd1fa
commit: 7c617d6ef79632221c7130359d05912e2405216a [5/6] tpm: Add vTPM TDX support
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240127/202401270147.6zANIFto-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240127/202401270147.6zANIFto-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/202401270147.6zANIFto-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/char/tpm/tpm_tdx.c:175: warning: Function parameter or struct member 'tdvmcall_status' not described in 'tdx_tpm_msg_resp'
>> drivers/char/tpm/tpm_tdx.c:175: warning: Function parameter or struct member 'service_cmd_status' not described in 'tdx_tpm_msg_resp'
>> drivers/char/tpm/tpm_tdx.c:175: warning: Function parameter or struct member 'rsvd' not described in 'tdx_tpm_msg_resp'
>> drivers/char/tpm/tpm_tdx.c:175: warning: Excess struct member 'rsvd1' description in 'tdx_tpm_msg_resp'
>> drivers/char/tpm/tpm_tdx.c:175: warning: Excess struct member 'rsvd2' description in 'tdx_tpm_msg_resp'
vim +175 drivers/char/tpm/tpm_tdx.c
141
142 /**
143 * struct tdx_tpm_msg_resp - TDX TPM message response format.
144 * @guid: A unique GUID to identify the TDVMCALL service.
145 * @buf_len: Length of the response buffer.
146 * @rsvd1: Reserved for future use.
147 * @service_ver: Version of TPM TDVMCALL command.
148 * @service_cmd: TPM TDVMCALL command
149 * TDVMCALL_TPM_SEND_MSG - 0x01
150 * TDVMCALL_TPM_RECV_MSG - 0x02
151 * @rsvd2: Reserved for future use.
152 * @spdm: SPDM Message header.
153 * @aad: SPDM AAD data.
154 * @app_data: SPDM application data.
155 *
156 * For more details, refer to TDX vTPM specification, r1.0, section titled
157 * "SPDM Secure Session Message Format".
158 */
159 struct tdx_tpm_msg_resp {
160 /* TDVMCALL service response header */
161 u8 guid[16];
162 u32 buf_len;
163 u32 tdvmcall_status;
164
165 /* TDVMCALL TPM Command Buffer response */
166 u8 service_ver;
167 u8 service_cmd;
168 u8 service_cmd_status;
169 u8 rsvd;
170
171 /* SPDM Message */
172 struct spdm_msg_hdr spdm;
173 struct spdm_aad aad;
174 struct spdm_data app_data;
> 175 } __packed;
176
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-26 17:59 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=202401270147.6zANIFto-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).