From: Greg KH <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: masahiroy@kernel.org, stable-commits@vger.kernel.org,
llvm@lists.linux.dev, linux-kbuild@vger.kernel.org
Subject: Re: Patch "modpost: Add '.ltext' and '.ltext.*' to TEXT_SECTIONS" has been added to the 6.6-stable tree
Date: Tue, 20 Feb 2024 08:44:26 +0100 [thread overview]
Message-ID: <2024022009-concur-slum-8043@gregkh> (raw)
In-Reply-To: <20240219190409.GB2348301@dev-arch.thelio-3990X>
On Mon, Feb 19, 2024 at 12:04:09PM -0700, Nathan Chancellor wrote:
> Hi Greg,
>
> On Mon, Feb 19, 2024 at 05:28:33PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > modpost: Add '.ltext' and '.ltext.*' to TEXT_SECTIONS
> >
> > to the 6.6-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > modpost-add-.ltext-and-.ltext.-to-text_sections.patch
> > and it can be found in the queue-6.6 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From 397586506c3da005b9333ce5947ad01e8018a3be Mon Sep 17 00:00:00 2001
> > From: Nathan Chancellor <nathan@kernel.org>
> > Date: Tue, 23 Jan 2024 15:59:55 -0700
> > Subject: modpost: Add '.ltext' and '.ltext.*' to TEXT_SECTIONS
> >
> > From: Nathan Chancellor <nathan@kernel.org>
> >
> > commit 397586506c3da005b9333ce5947ad01e8018a3be upstream.
>
> Please apply upstream commit 6a4e59eeedc3 ("linux/init: remove __memexit*
> annotations") before this change, as there is a warning in modpost
> without it:
>
> scripts/mod/modpost.c:916:37: warning: excess elements in array initializer [-Wexcess-initializers]
> 916 | .good_tosec = {ALL_TEXT_SECTIONS , NULL},
> | ^~~~
> .../lib/clang/19/include/__stddef_null.h:26:14: note: expanded from macro 'NULL'
> 26 | #define NULL ((void*)0)
> | ^~~~~~~~~~
> 1 warning generated.
>
> It applies cleanly with 'git format-patch | patch' for me and I don't
> think it is unreasonable as a fix for this issue in stable.
>
> This will be needed in 6.1 as well but that backport is a little more
> involved, I will reply there with an mbox series.
Thanks, that fixed the build warning!
greg k-h
prev parent reply other threads:[~2024-02-20 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024021932-overpass-stinger-b897@gregkh>
2024-02-19 19:04 ` Patch "modpost: Add '.ltext' and '.ltext.*' to TEXT_SECTIONS" has been added to the 6.6-stable tree Nathan Chancellor
2024-02-20 7:44 ` Greg KH [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=2024022009-concur-slum-8043@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=stable-commits@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).