Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: stable@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	adobriyan@gmail.com
Subject: Re: GCC 15 and stable kernels
Date: Mon, 28 Apr 2025 18:47:41 +0200	[thread overview]
Message-ID: <2025042802-cozily-caddy-8625@gregkh> (raw)
In-Reply-To: <c6867c6c-bc47-4e3c-9676-70184baf21db@googlemail.com>

On Mon, Apr 28, 2025 at 04:08:27PM +0100, Chris Clayton wrote:
> On 28/04/2025 12:22, Greg Kroah-Hartman wrote:
> > On Mon, Apr 28, 2025 at 12:14:09PM +0100, Chris Clayton wrote:
> >> Hi Greg,
> >>
> >> I've built the four stable kernels that were released on 25 April. I found that to successfully build with GCC-15, each
> >> of them required backports of one or both of two upstream commits. Those commits are:
> >>
> >> Title		Commit						Author	
> >> nonstring 	9d7a0577c9db35c4cc52db90bc415ea248446472  	Linus
> >> gnu11		b3bee1e7c3f2b1b77182302c7b2131c804175870	Alexey Dobriyan
> >>
> >> 6.14.4 and 6.12.25 required only nonstring. 6.6.87 required only gnu11, 6.1.35 required both.
> >>
> >> Additionally, chasing down why my new Bluetooth mouse doesn't work, I also had cause to build 5.15.180 and found that it
> >> needed gnull.
> >>
> >> I have TO dash out now, but I could send you a zip archive of the patches later today, if that would help.
> > 
> > Please send backported patches of the above, as they do not apply
> > 
> 
> The patches are in the attached tarball.

Please submit them as a proper patch, with the original changelog and
authorship information intact.  We have thousands of examples of this on
the stable mailing list for how this should be done.

thanks,

greg k-h

      reply	other threads:[~2025-04-28 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 11:14 GCC 15 and stable kernels Chris Clayton
2025-04-28 11:22 ` Greg Kroah-Hartman
2025-04-28 15:08   ` Chris Clayton
2025-04-28 16:47     ` 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=2025042802-cozily-caddy-8625@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=adobriyan@gmail.com \
    --cc=chris2553@googlemail.com \
    --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