All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maximilian Luz <luzmaximilian@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Steev Klimaszewski <steev@kali.org>,
	Johan Hovold <johan+linaro@kernel.org>
Subject: [steev:lenovo-x13s-v6.5-rc7 64/129] drivers/firmware/qcom_qseecom_uefisecapp.c:172: warning: Function parameter or member 'guid_offset' not described in 'qsee_rsp_uefi_get_next_variable'
Date: Fri, 25 Aug 2023 10:30:48 +0800	[thread overview]
Message-ID: <202308251028.BnSdu23P-lkp@intel.com> (raw)

tree:   https://github.com/steev/linux lenovo-x13s-v6.5-rc7
head:   68f425346397c1806f828d4ee58e9468c924f408
commit: e54a5193d61abc174dff575a57c7530d0b62863f [64/129] firmware: Add support for Qualcomm UEFI Secure Application
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20230825/202308251028.BnSdu23P-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230825/202308251028.BnSdu23P-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/202308251028.BnSdu23P-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/firmware/qcom_qseecom_uefisecapp.c:172: warning: Function parameter or member 'guid_offset' not described in 'qsee_rsp_uefi_get_next_variable'


vim +172 drivers/firmware/qcom_qseecom_uefisecapp.c

   149	
   150	/**
   151	 * struct qsee_rsp_uefi_get_next_variable - Response for the
   152	 * GetNextVariableName command.
   153	 * @command_id:  The ID of the command. Should be
   154	 *               %QSEE_CMD_UEFI_GET_NEXT_VARIABLE.
   155	 * @length:      Length of the response in bytes, including this struct and any
   156	 *               parameters (name, GUID) stored after it as well as any padding
   157	 *               thereof for alignment.
   158	 * @status:      Status of this command.
   159	 * @guid_size:   Size of the GUID parameter in bytes, i.e. sizeof(efi_guid_t).
   160	 * @name_offset: Offset from the start of this struct to where the variable
   161	 *               name is stored (as utf-16 string), in bytes.
   162	 * @name_size:   Size of the name parameter in bytes, including null-terminator.
   163	 */
   164	struct qsee_rsp_uefi_get_next_variable {
   165		u32 command_id;
   166		u32 length;
   167		u32 status;
   168		u32 guid_offset;
   169		u32 guid_size;
   170		u32 name_offset;
   171		u32 name_size;
 > 172	} __packed;
   173	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-08-25  2:31 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=202308251028.BnSdu23P-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=johan+linaro@kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=steev@kali.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.