From: Sean Christopherson <seanjc@google.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Mark Brown <broonie@kernel.org>,
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: Wed, 27 May 2026 08:33:03 -0700 [thread overview]
Message-ID: <ahcOr_dZGhWspNG6@google.com> (raw)
In-Reply-To: <ahVN8WXF5WRX-Y_1@monoceros>
On Tue, May 26, 2026, Uwe Kleine-König wrote:
> 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).
Build bots reported this as well[*], but next-20260527 looks correct so I assume
Mark already handled this?
[*] https://lore.kernel.org/all/202605272110.QiNGdptX-lkp@intel.com
next prev parent reply other threads:[~2026-05-27 15:33 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
2026-05-27 15:33 ` Sean Christopherson [this message]
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=ahcOr_dZGhWspNG6@google.com \
--to=seanjc@google.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.