From: Alexey Gladkov <legion@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Nicolas Schier <nsc@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
Linux Kernel Functional Testing <lkft@linaro.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/3] kbuild: Fixes for fallout from recent modules.builtin.modinfo series
Date: Fri, 10 Oct 2025 09:19:01 +0200 [thread overview]
Message-ID: <aOizZcGLEH9edZQ0@example.org> (raw)
In-Reply-To: <20251008-kbuild-fix-modinfo-regressions-v1-0-9fc776c5887c@kernel.org>
On Wed, Oct 08, 2025 at 03:46:43PM -0700, Nathan Chancellor wrote:
> Hi all,
>
> This is a series to address some problems that were exposed by the
> recent modules.builtin.modinfo series that landed in commit c7d3dd9163e6
> ("Merge patch series "Add generated modalias to
> modules.builtin.modinfo"").
>
> The third patch is not directly related to the aforementioned series, as
> the warning it fixes happens prior to the series but commit 8d18ef04f940
> ("s390: vmlinux.lds.S: Reorder sections") from the series creates
> conflicts in this area, so I included it here.
>
> I plan to send at least the first two patches to Linus by Saturday for
> -rc1 but I will take the third with an Ack.
>
> ---
> Nathan Chancellor (3):
> kbuild: Restore pattern to avoid stripping .rela.dyn from vmlinux
> kbuild: Add '.rel.*' strip pattern for vmlinux
> s390/vmlinux.lds.S: Move .vmlinux.info to end of allocatable sections
>
> arch/s390/kernel/vmlinux.lds.S | 44 +++++++++++++++++++++---------------------
> scripts/Makefile.vmlinux | 5 ++++-
> 2 files changed, 26 insertions(+), 23 deletions(-)
> ---
> base-commit: 38492c5743f8b7213ca86f0cd72ea625af35d5ef
> change-id: 20251008-kbuild-fix-modinfo-regressions-95e3fd151dec
>
> Best regards,
> --
> Nathan Chancellor <nathan@kernel.org>
>
Acked-by: Alexey Gladkov <legion@kernel.org>
--
Rgrds, legion
prev parent reply other threads:[~2025-10-10 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 22:46 [PATCH 0/3] kbuild: Fixes for fallout from recent modules.builtin.modinfo series Nathan Chancellor
2025-10-08 22:46 ` [PATCH 1/3] kbuild: Restore pattern to avoid stripping .rela.dyn from vmlinux Nathan Chancellor
2025-10-10 17:13 ` Ard Biesheuvel
2025-10-08 22:46 ` [PATCH 2/3] kbuild: Add '.rel.*' strip pattern for vmlinux Nathan Chancellor
2025-10-10 17:16 ` Ard Biesheuvel
2025-10-08 22:46 ` [PATCH 3/3] s390/vmlinux.lds.S: Move .vmlinux.info to end of allocatable sections Nathan Chancellor
2025-10-09 11:37 ` Alexander Gordeev
2025-10-09 19:44 ` [PATCH 0/3] kbuild: Fixes for fallout from recent modules.builtin.modinfo series Nicolas Schier
2025-10-10 7:19 ` Alexey Gladkov [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=aOizZcGLEH9edZQ0@example.org \
--to=legion@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=alexghiti@rivosinc.com \
--cc=ardb@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=svens@linux.ibm.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.