public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>
Subject: drivers/firmware/efi/capsule-loader.c:84:12: warning: no previous declaration for 'efi_capsule_setup_info'
Date: Sat, 9 Apr 2022 01:56:11 +0800	[thread overview]
Message-ID: <202204090125.wgI0L7F3-lkp@intel.com> (raw)

Hi Ard,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   1831fed559732b132aef0ea8261ac77e73f7eadf
commit: 3fabd628d5ea24b02ddb1230ffca1df0f779f84e efi/capsule-loader: Redirect calls to efi_capsule_setup_info() via weak alias
date:   4 years, 10 months ago
config: i386-randconfig-a005 (https://download.01.org/0day-ci/archive/20220409/202204090125.wgI0L7F3-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3fabd628d5ea24b02ddb1230ffca1df0f779f84e
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 3fabd628d5ea24b02ddb1230ffca1df0f779f84e
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/platform/efi/ drivers/firmware/efi/ drivers/net/dsa/ fs/f2fs/ fs/xfs/ net/sunrpc/xprtrdma/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> drivers/firmware/efi/capsule-loader.c:84:12: warning: no previous declaration for 'efi_capsule_setup_info' [-Wmissing-declarations]
    int __weak efi_capsule_setup_info(struct capsule_info *cap_info, void *kbuff,
               ^~~~~~~~~~~~~~~~~~~~~~


vim +/efi_capsule_setup_info +84 drivers/firmware/efi/capsule-loader.c

    72	
    73	/**
    74	 * efi_capsule_setup_info - obtain the efi capsule header in the binary and
    75	 *			    setup capsule_info structure
    76	 * @cap_info: pointer to current instance of capsule_info structure
    77	 * @kbuff: a mapped first page buffer pointer
    78	 * @hdr_bytes: the total received number of bytes for efi header
    79	 *
    80	 * Platforms with non-standard capsule update mechanisms can override
    81	 * this __weak function so they can perform any required capsule
    82	 * image munging. See quark_quirk_function() for an example.
    83	 **/
  > 84	int __weak efi_capsule_setup_info(struct capsule_info *cap_info, void *kbuff,
    85					  size_t hdr_bytes)
    86	{
    87		/* Only process data block that is larger than efi header size */
    88		if (hdr_bytes < sizeof(efi_capsule_header_t))
    89			return 0;
    90	
    91		memcpy(&cap_info->header, kbuff, sizeof(cap_info->header));
    92		cap_info->total_size = cap_info->header.imagesize;
    93	
    94		return __efi_capsule_setup_info(cap_info);
    95	}
    96	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-04-08 17:57 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=202204090125.wgI0L7F3-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox