From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: Backports of d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca for 6.6 and older
Date: Tue, 17 Jun 2025 16:09:48 +0200 [thread overview]
Message-ID: <2025061727-greyhound-lurch-d1f6@gregkh> (raw)
In-Reply-To: <20250604235159.GA4185199@ax162>
On Wed, Jun 04, 2025 at 04:51:59PM -0700, Nathan Chancellor wrote:
> Hi Greg,
>
> On Tue, May 27, 2025 at 05:19:34PM +0200, Greg Kroah-Hartman wrote:
> > On Fri, May 23, 2025 at 02:17:10PM -0700, Nathan Chancellor wrote:
> > > Hi Greg and Sasha,
> > >
> > > Please find attached backports of commit d0afcfeb9e38 ("kbuild: Disable
> > > -Wdefault-const-init-unsafe") for 6.6 and older, which is needed for tip
> > > of tree versions of LLVM. Please let me know if there are any questions.
> >
> > All now queued up, thanks!
>
> It looks like the 6.6 backport got lost?
>
> $ rg d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca
> releases/6.1.141/kbuild-disable-wdefault-const-init-unsafe.patch:commit d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca upstream.
> releases/5.4.294/kbuild-disable-wdefault-const-init-unsafe.patch:commit d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca upstream.
> releases/5.15.185/kbuild-disable-wdefault-const-init-unsafe.patch:commit d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca upstream.
> releases/5.10.238/kbuild-disable-wdefault-const-init-unsafe.patch:commit d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca upstream.
> releases/6.14.8/kbuild-disable-wdefault-const-init-unsafe.patch:From d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca Mon Sep 17 00:00:00 2001
> releases/6.14.8/kbuild-disable-wdefault-const-init-unsafe.patch:commit d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca upstream.
> releases/6.12.30/kbuild-disable-wdefault-const-init-unsafe.patch:From d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca Mon Sep 17 00:00:00 2001
> releases/6.12.30/kbuild-disable-wdefault-const-init-unsafe.patch:commit d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca upstream.
>
> Are you able to pull it from the original message? It still applies
> cleanly for me.
Odd, it did not apply cleanly at all for me. I've hand-applied it now,
thanks for catching this.
greg k-h
prev parent reply other threads:[~2025-06-17 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 21:17 Backports of d0afcfeb9e3810ec89d1ffde1a0e36621bb75dca for 6.6 and older Nathan Chancellor
2025-05-27 15:19 ` Greg Kroah-Hartman
2025-06-04 23:51 ` Nathan Chancellor
2025-06-17 14:09 ` Greg Kroah-Hartman [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=2025061727-greyhound-lurch-d1f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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