From: kbuild test robot <lkp@intel.com>
To: Matthew Garrett <matthewgarrett@google.com>
Cc: kbuild-all@lists.01.org, linux-efi@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>
Subject: [efi:next 16/20] arch/arm/include/asm/efi.h:53:32: warning: 'pci_handle' is used uninitialized in this function
Date: Fri, 3 Jan 2020 03:18:19 +0800 [thread overview]
Message-ID: <202001030335.E28ujClK%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2503 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
head: d6e40eca3ddb5408148b8875e18dd54384aaa796
commit: 4e3a2778404ecb47665318addc8092f5b749efb4 [16/20] efi: Allow disabling PCI busmastering on bridges during boot
config: arm-multi_v7_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 4e3a2778404ecb47665318addc8092f5b749efb4
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/firmware/efi/libstub/pci.c:12:0:
drivers/firmware/efi/libstub/pci.c: In function 'efi_pci_disable_bridge_busmaster':
>> arch/arm/include/asm/efi.h:53:32: warning: 'pci_handle' is used uninitialized in this function [-Wuninitialized]
#define efi_bs_call(func, ...) efi_system_table()->boottime->func(__VA_ARGS__)
^~~~~~~~~~~~~~~~
--
In file included from drivers/firmware//efi/libstub/pci.c:12:0:
drivers/firmware//efi/libstub/pci.c: In function 'efi_pci_disable_bridge_busmaster':
>> arch/arm/include/asm/efi.h:53:32: warning: 'pci_handle' is used uninitialized in this function [-Wuninitialized]
#define efi_bs_call(func, ...) efi_system_table()->boottime->func(__VA_ARGS__)
^~~~~~~~~~~~~~~~
vim +/pci_handle +53 arch/arm/include/asm/efi.h
81a0bc39ea1960 Roy Franz 2015-09-23 52
966291f6344d7e Ard Biesheuvel 2019-12-24 @53 #define efi_bs_call(func, ...) efi_system_table()->boottime->func(__VA_ARGS__)
966291f6344d7e Ard Biesheuvel 2019-12-24 54 #define efi_rt_call(func, ...) efi_system_table()->runtime->func(__VA_ARGS__)
f958efe9759683 Ard Biesheuvel 2019-12-24 55 #define efi_is_native() (true)
81a0bc39ea1960 Roy Franz 2015-09-23 56
:::::: The code at line 53 was first introduced by commit
:::::: 966291f6344d7eb6fc3204381a426bafa20a3d18 efi/libstub: Rename efi_call_early/_runtime macros to be more intuitive
:::::: TO: Ard Biesheuvel <ardb@kernel.org>
:::::: CC: Ingo Molnar <mingo@kernel.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 49460 bytes --]
reply other threads:[~2020-01-02 19:18 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=202001030335.E28ujClK%lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-efi@vger.kernel.org \
--cc=matthewgarrett@google.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).