From: kernel test robot <lkp@intel.com>
To: Khalid Ali <khaliidcaliy@gmail.com>,
ardb@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
hpa@zytor.com, x86@kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, Khalid Ali <khaliidcaliy@gmail.com>
Subject: Re: [PATCH] x86/efi: error handling on efi memory map
Date: Sun, 8 Jun 2025 21:22:01 +0800 [thread overview]
Message-ID: <202506082104.4eSjYWTe-lkp@intel.com> (raw)
In-Reply-To: <20250608090356.1115-1-khaliidcaliy@gmail.com>
Hi Khalid,
kernel test robot noticed the following build errors:
[auto build test ERROR on efi/next]
[also build test ERROR on tip/master tip/auto-latest linus/master v6.15 next-20250606]
[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/Khalid-Ali/x86-efi-error-handling-on-efi-memory-map/20250608-170711
base: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
patch link: https://lore.kernel.org/r/20250608090356.1115-1-khaliidcaliy%40gmail.com
patch subject: [PATCH] x86/efi: error handling on efi memory map
config: i386-buildonly-randconfig-002-20250608 (https://download.01.org/0day-ci/archive/20250608/202506082104.4eSjYWTe-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250608/202506082104.4eSjYWTe-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/202506082104.4eSjYWTe-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/platform/efi/efi_32.c:90:13: error: conflicting types for 'efi_map_region_fixed'
90 | void __init efi_map_region_fixed(efi_memory_desc_t *md) {}
| ^
arch/x86/include/asm/efi.h:131:19: note: previous declaration is here
131 | extern int __init efi_map_region_fixed(efi_memory_desc_t *md);
| ^
1 error generated.
vim +/efi_map_region_fixed +90 arch/x86/platform/efi/efi_32.c
d2f7cbe7b26a74 Borislav Petkov 2013-10-31 89
3b2664964bc886 Dave Young 2013-12-20 @90 void __init efi_map_region_fixed(efi_memory_desc_t *md) {}
1fec0533693cd7 Dave Young 2013-12-20 91 void __init parse_efi_setup(u64 phys_addr, u32 data_len) {}
3b2664964bc886 Dave Young 2013-12-20 92
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-06-08 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 8:59 Khalid Ali
2025-06-08 13:22 ` kernel test robot [this message]
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=202506082104.4eSjYWTe-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=khaliidcaliy@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®