From: kernel test robot <lkp@intel.com>
To: "Marek Marczykowski-Górecki " <marmarek@invisiblethingslab.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-efi@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>
Subject: [efi:next 1/4] drivers/firmware/efi/efi.c:1009:44: warning: passing argument 2 of 'efi_mem_desc_lookup' discards 'const' qualifier from pointer target type
Date: Tue, 10 Mar 2026 18:17:44 +0100 [thread overview]
Message-ID: <202603101851.bAhG7uGN-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
head: c8da97cbb39c4c043d8456fcae25aa921c844a3f
commit: 5992265762e666564b0275d72e54c514ab20c7f3 [1/4] efi: make efi_mem_type() and efi_mem_attributes() work on Xen PV
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260310/202603101851.bAhG7uGN-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260310/202603101851.bAhG7uGN-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/202603101851.bAhG7uGN-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/firmware/efi/efi.c: In function 'efi_mem_type':
>> drivers/firmware/efi/efi.c:1009:44: warning: passing argument 2 of 'efi_mem_desc_lookup' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
1009 | if (efi_mem_desc_lookup(phys_addr, &md))
| ^~~
In file included from drivers/firmware/efi/efi.c:22:
include/linux/efi.h:757:66: note: expected 'efi_memory_desc_t *' but argument is of type 'const efi_memory_desc_t *'
757 | extern int efi_mem_desc_lookup(u64 phys_addr, efi_memory_desc_t *out_md);
| ~~~~~~~~~~~~~~~~~~~^~~~~~
vim +1009 drivers/firmware/efi/efi.c
993
994 /*
995 * efi_mem_type - lookup memmap type for physical address
996 * @phys_addr: the physical address to lookup
997 *
998 * Search in the EFI memory map for the region covering @phys_addr.
999 * Returns the EFI memory type if the region was found in the memory
1000 * map, -EINVAL otherwise.
1001 */
1002 int efi_mem_type(unsigned long phys_addr)
1003 {
1004 const efi_memory_desc_t md;
1005
1006 if (!efi_enabled(EFI_MEMMAP) && !efi_enabled(EFI_PARAVIRT))
1007 return -ENOTSUPP;
1008
> 1009 if (efi_mem_desc_lookup(phys_addr, &md))
1010 return -EINVAL;
1011
1012 return md.type;
1013 }
1014
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-10 17: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=202603101851.bAhG7uGN-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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