From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Maxim Kochetkov <fido_max@inbox.ru>,
Romain Naour <romain.naour@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] toolchain/Config.in: extend gcc bug 43744 to every sh architecture
Date: Sun, 5 Feb 2023 13:15:59 +0100 [thread overview]
Message-ID: <20230205131559.6f79944f@windsurf> (raw)
In-Reply-To: <20230202154239.325711-1-giulio.benetti@benettiengineering.com>
On Thu, 2 Feb 2023 16:42:38 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
It would be nice to have a non-empty commit log, which explains which
other CPU is affected by the bug, and perhaps a defconfig that exhibits
the issue, or something like that.
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-05 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 15:42 [Buildroot] [PATCH 1/2] toolchain/Config.in: extend gcc bug 43744 to every sh architecture Giulio Benetti
2023-02-02 15:42 ` [Buildroot] [PATCH 2/2] package/postgresql: work around gcc bug 43744 Giulio Benetti
2023-02-06 11:21 ` Thomas Petazzoni via buildroot
2023-02-06 13:26 ` Giulio Benetti
2023-02-22 16:22 ` Peter Korsgaard
2023-02-05 12:15 ` Thomas Petazzoni via buildroot [this message]
2023-02-05 21:25 ` [Buildroot] [PATCH v2] toolchain/Config.in: extend gcc bug 43744 to every sh architecture Giulio Benetti
2023-02-06 9:46 ` Thomas Petazzoni via buildroot
2023-02-22 15:48 ` Peter Korsgaard
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=20230205131559.6f79944f@windsurf \
--to=buildroot@buildroot.org \
--cc=fido_max@inbox.ru \
--cc=giulio.benetti@benettiengineering.com \
--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 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.