From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Peter Seiderer <ps.report@gmx.net>,
Julien Corjon <corjon.j@ecagroup.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 1/2] toolchain/Config.in: update gcc bug 90620
Date: Sun, 18 Sep 2022 23:15:47 +0200 [thread overview]
Message-ID: <877d20fkos.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220910135256.1689860-1-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Sat, 10 Sep 2022 15:52:55 +0200")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> Gcc bug 90620 reappeared with gcc 11.x so let's update
> BR2_TOOLCHAIN_HAS_GCC_BUG_90620 conditions.
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Committed to 2022.02.x, 2022.05.x and 2022.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-09-18 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 13:52 [Buildroot] [PATCH 1/2] toolchain/Config.in: update gcc bug 90620 Giulio Benetti
2022-09-10 13:52 ` [Buildroot] [PATCH 2/2] package/qt5/qt5xmlpatterns: fix build failure due to " Giulio Benetti
2022-09-11 19:45 ` Yann E. MORIN
2022-09-18 21:15 ` Peter Korsgaard
2022-09-11 19:30 ` [Buildroot] [PATCH 1/2] toolchain/Config.in: update " Yann E. MORIN
2022-09-11 19:43 ` Giulio Benetti
2022-09-11 19:54 ` Yann E. MORIN
2022-09-18 21:15 ` Peter Korsgaard [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=877d20fkos.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=corjon.j@ecagroup.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=ps.report@gmx.net \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox