From: Mark Brown <broonie@kernel.org>
To: "Ard Biesheuvel" <ardb@kernel.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the efi tree
Date: Tue, 10 Mar 2026 19:06:42 +0000 [thread overview]
Message-ID: <abBrwtoAg8oKcImt@sirena.org.uk> (raw)
Hi all,
After merging the efi tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
/tmp/next/build/drivers/firmware/efi/efi.c: In function 'efi_mem_type':
/tmp/next/build/drivers/firmware/efi/efi.c:1009:44: error: passing argument 2 of 'efi_mem_desc_lookup' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
1009 | if (efi_mem_desc_lookup(phys_addr, &md))
| ^~~
In file included from /tmp/next/build/drivers/firmware/efi/efi.c:22:
/tmp/next/build/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);
| ~~~~~~~~~~~~~~~~~~~^~~~~~
Caused by commit
5992265762e66 (efi: make efi_mem_type() and efi_mem_attributes() work on Xen PV)
I have used the tree from 20260309 instead.
next reply other threads:[~2026-03-10 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 19:06 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-09 10:21 linux-next: build failure after merge of the efi tree Stephen Rothwell
2025-07-09 10:23 ` Ard Biesheuvel
2023-08-22 6:48 Stephen Rothwell
2023-08-22 7:32 ` Ard Biesheuvel
2023-08-22 8:08 ` Stephen Rothwell
2023-08-22 8:41 ` Ard Biesheuvel
2022-09-19 9:11 Stephen Rothwell
2022-09-19 9:12 ` Ard Biesheuvel
2022-09-19 9:25 ` Ard Biesheuvel
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=abBrwtoAg8oKcImt@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marmarek@invisiblethingslab.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