From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jari Ruusu <jariruusu@protonmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 5.10 00/59] 5.10.223-rc1 review
Date: Tue, 13 Aug 2024 12:32:14 +0200 [thread overview]
Message-ID: <2024081303-quotable-legroom-1850@gregkh> (raw)
In-Reply-To: <2024072627-pasture-denim-0390@gregkh>
On Fri, Jul 26, 2024 at 12:23:02PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jul 26, 2024 at 09:53:18AM +0000, Jari Ruusu wrote:
> > On Friday, July 26th, 2024 at 11:52, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > > Also the "Fixes:" tag is not in the correct format, please fix that up
> > > at the very least.
> >
> > Some older systems still compile kernels with old gcc version.
> > These warnings and errors show up when compiling with gcc 4.9.2
> >
> > error: "__GCC4_has_attribute___uninitialized__" is not defined [-Werror=undef]
> >
> > Following patch fixes this. Upstream won't need this because
> > newer kernels are not compilable with gcc 4.9.
> >
> > Subject: gcc-4.9 warning/error fix for 5.10.223-rc1
> > Fixes: fd7eea27a3ae ("Compiler Attributes: Add __uninitialized macro")
> > Signed-off-by: Jari Ruusu <jariruusu@protonmail.com>
> >
> > --- ./include/linux/compiler_attributes.h.OLD
> > +++ ./include/linux/compiler_attributes.h
> > @@ -37,6 +37,7 @@
> > # define __GCC4_has_attribute___nonstring__ 0
> > # define __GCC4_has_attribute___no_sanitize_address__ (__GNUC_MINOR__ >= 8)
> > # define __GCC4_has_attribute___no_sanitize_undefined__ (__GNUC_MINOR__ >= 9)
> > +# define __GCC4_has_attribute___uninitialized__ 0
> > # define __GCC4_has_attribute___fallthrough__ 0
> > # define __GCC4_has_attribute___warning__ 1
> > #endif
> >
> > --
> > Jari Ruusu 4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD ACDF F073 3C80 8132 F189
> >
>
> Better, thanks! I'll touch this up by hand and apply it to the relevant
> branches (not just this one needs it), for the next round of stable
> releases.
Now queued up.
greg k-h
next prev parent reply other threads:[~2024-08-13 10:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 7:25 [PATCH 5.10 00/59] 5.10.223-rc1 review Jari Ruusu
2024-07-26 7:49 ` Greg Kroah-Hartman
2024-07-26 8:21 ` Jari Ruusu
2024-07-26 8:52 ` Greg Kroah-Hartman
2024-07-26 9:53 ` Jari Ruusu
2024-07-26 10:23 ` Greg Kroah-Hartman
2024-08-13 10:32 ` Greg Kroah-Hartman [this message]
2024-07-26 10:00 ` Shreeya Patel
-- strict thread matches above, loose matches on Subject: below --
2024-07-25 14:36 Greg Kroah-Hartman
2024-07-25 17:36 ` ChromeOS Kernel Stable Merge
2024-07-26 4:19 ` Dominique Martinet
2024-07-26 8:10 ` Pavel Machek
2024-07-26 11:35 ` Mark Brown
2024-07-26 17:12 ` Jon Hunter
2024-07-26 17:27 ` Florian Fainelli
2024-07-26 17:33 ` Naresh Kamboju
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=2024081303-quotable-legroom-1850@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jariruusu@protonmail.com \
--cc=linux-kernel@vger.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 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.