From: Mike Rapoport <rppt@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-nonmm-unstable tree
Date: Tue, 29 Jul 2025 12:14:51 +0300 [thread overview]
Message-ID: <aIiRC8fXiOXKbPM_@kernel.org> (raw)
In-Reply-To: <20250729150042.77832045@canb.auug.org.au>
On Tue, Jul 29, 2025 at 03:00:42PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm-nonmm-unstable tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> WARNING: modpost: vmlinux: section mismatch in reference: kho_test_restore+0x16c (section: .text.unlikely) -> kho_test_restore_data.isra.0 (section: .init.text)
>
> Introduced by commit
>
> c2d288f7ab13 ("kho: add test for kexec handover")
This should fix it. Andrew can you please add it as a fixup?
diff --git a/lib/test_kho.c b/lib/test_kho.c
index f5fe39c7c2b1..c2eb899c3b45 100644
--- a/lib/test_kho.c
+++ b/lib/test_kho.c
@@ -194,7 +194,7 @@ static int kho_test_save(void)
return register_kho_notifier(&kho_test_nb);
}
-static int __init kho_test_restore_data(const void *fdt, int node)
+static int kho_test_restore_data(const void *fdt, int node)
{
const unsigned int *nr_folios;
const phys_addr_t *folios_info;
> --
> Cheers,
> Stephen Rothwell
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-07-29 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 5:00 linux-next: build warning after merge of the mm-nonmm-unstable tree Stephen Rothwell
2025-07-29 9:14 ` Mike Rapoport [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-26 1:55 Stephen Rothwell
2025-11-26 13:55 ` Breno Leitao
2025-11-26 16:44 ` Andrew Morton
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=aIiRC8fXiOXKbPM_@kernel.org \
--to=rppt@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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