From: "Uwe Kleine-König" <u.kleine-koenig@baylibre•com>
To: Mark Brown <broonie@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for May 25
Date: Tue, 26 May 2026 09:51:29 +0200 [thread overview]
Message-ID: <ahVN8WXF5WRX-Y_1@monoceros> (raw)
In-Reply-To: <ahSDZV9eR6zJ1pxG@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Hello Mark,
I got a build failure and I think this is due to a mis-merge in next:
WARNING: modpost: vmlinux: section mismatch in reference: tdx_module_run_update.cold+0x8 (section: .text.unlikely) -> get_tdx_sys_info_version (section: .init.text)
ERROR: modpost: Section mismatches detected.
Set CONFIG_SECTION_MISMATCH_WARN_ONLY=y to allow them.
Commit 6e49a980dea9 ("x86/virt/tdx: Refresh TDX module version after
update") drops the __init annotation from get_tdx_sys_info_version() in
arch/x86/virt/vmx/tdx/tdx_global_metadata.c
In commit f2deea555964 ("Merge branch 'next' of
https://github.com/kvm-x86/linux.git") the __init is readded however.
When I try to merge the two parents of f2deea555964 to reproduce the
issue, git gets it right for me without a merge conflict (in that file).
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-05-26 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 17:14 linux-next: Tree for May 25 Mark Brown
2026-05-26 7:51 ` Uwe Kleine-König [this message]
2026-05-27 15:33 ` Sean Christopherson
2026-05-27 16:03 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-05-25 3:49 Stephen Rothwell
2022-05-25 6:39 Stephen Rothwell
2021-05-25 6:39 Stephen Rothwell
2020-05-25 12:49 Stephen Rothwell
2017-05-25 2:43 Stephen Rothwell
2016-05-25 3:44 Stephen Rothwell
2015-05-25 12:02 Stephen Rothwell
2011-05-25 3:58 Stephen Rothwell
2010-05-25 4:26 Stephen Rothwell
2009-05-25 8:55 Stephen Rothwell
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=ahVN8WXF5WRX-Y_1@monoceros \
--to=u.kleine-koenig@baylibre$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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