From: Peter Schneider <pschneider1968@googlemail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.1.133
Date: Mon, 7 Apr 2025 17:24:13 +0200 [thread overview]
Message-ID: <f41ffdf9-245a-469e-9fd2-4b4b6c013b5d@googlemail.com> (raw)
In-Reply-To: <2025040752-army-degrease-7703@gregkh>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
Hi Greg,
Am 07.04.2025 um 10:19 schrieb Greg Kroah-Hartman:
> I'm announcing the release of the 6.1.133 kernel.
>
> All users of the 6.1 kernel series must upgrade.
When building 6.1.133, I get a warning in phase MODPOST about a section mismatch. I'm sure
I didn't get this warning in -rc1.
I also have no clue whether this is important or serious in any way or whether it can be
safely ignored. I just wanted to let you know about it, so that you can have a look into it.
GEN modules.builtin
GEN .vmlinux.objs
MODPOST Module.symvers
WARNING: modpost: vmlinux.o: section mismatch in reference: pci_xen_swiotlb_init_late
(section: .text) -> xen_swiotlb_fixup (section: .init.text)
CC .vmlinux.export.o
UPD include/generated/utsversion.h
CC init/version-timestamp.o
Building on X86_64 (2-socket Ivy Bridge Xeon E5-2697 v2 server) with "make -j48", config
attached. The remainder of the build works fine without further warnings or errors, and
the machine boots and works just fine so far with the built kernel.
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
[-- Attachment #2: .config --]
[-- Type: application/xml, Size: 272849 bytes --]
prev parent reply other threads:[~2025-04-07 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 8:19 Linux 6.1.133 Greg Kroah-Hartman
2025-04-07 8:19 ` Greg Kroah-Hartman
2025-04-07 15:24 ` Peter Schneider [this message]
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=f41ffdf9-245a-469e-9fd2-4b4b6c013b5d@googlemail.com \
--to=pschneider1968@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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