public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Brauner <brauner@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the vfs-brauner tree
Date: Wed, 5 Mar 2025 21:55:06 +1100	[thread overview]
Message-ID: <20250305215506.1f34f920.ddiss@suse.de> (raw)
In-Reply-To: <20250305210702.66402528@canb.auug.org.au>

Hi Stephen,

On Wed, 5 Mar 2025 21:07:02 +1100, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the vfs-brauner tree, today's linux-next build (powerpc
> allyesconfig) produced these warnings:
> 
> WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x0 (section: .data) -> initramfs_test_extract (section: .init.text)
> WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x30 (section: .data) -> initramfs_test_fname_overrun (section: .init.text)
> WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x60 (section: .data) -> initramfs_test_data (section: .init.text)
> WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0x90 (section: .data) -> initramfs_test_csum (section: .init.text)
> WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0xc0 (section: .data) -> initramfs_test_hardlink (section: .init.text)
> WARNING: modpost: vmlinux: section mismatch in reference: initramfs_test_cases+0xf0 (section: .data) -> initramfs_test_many (section: .init.text)
> 
> Introduced by commit
> 
>   b6736cfccb58 ("initramfs_test: kunit tests for initramfs unpacking")

The new warnings are being discussed in a thread at:
https://lore.kernel.org/linux-kselftest/20250305114701.28c0ee0b.ddiss@suse.de/T/#u

Thanks, David

  reply	other threads:[~2025-03-05 10:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 10:07 linux-next: build warnings after merge of the vfs-brauner tree Stephen Rothwell
2025-03-05 10:55 ` David Disseldorp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-16  0:52 Stephen Rothwell
2025-11-17  6:47 Stephen Rothwell
2025-11-12  2:42 Stephen Rothwell
2025-11-12 10:10 ` Mateusz Guzik
2025-11-12 10:55   ` Stephen Rothwell
2025-11-12 10:57     ` Mateusz Guzik
2025-07-17  7:36 Stephen Rothwell
2025-07-22 10:24 ` Jann Horn
2024-12-13  4:27 Stephen Rothwell
2024-12-19  6:32 ` Stephen Rothwell
2025-01-14  5:48   ` Stephen Rothwell
2025-01-20  8:25     ` Stephen Rothwell
2025-01-20 12:15       ` Christian Brauner
2025-01-20 20:55         ` Stephen Rothwell
2024-12-11  3:37 Stephen Rothwell
2024-12-19  6:31 ` Stephen Rothwell
2024-12-19 12:40   ` Jeff Layton
2024-12-19 20:36     ` Stephen Rothwell
2025-01-06 13:50       ` Geert Uytterhoeven
2024-10-09  6:29 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=20250305215506.1f34f920.ddiss@suse.de \
    --to=ddiss@suse.de \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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