From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Michael Nosthoff <buildroot@heine.tech>,
Maxim Kochetkov <fido_max@inbox.ru>,
buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
Matt Weber <matthew.weber@collins.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH v2] toolchain: remove binutils bug 21464
Date: Mon, 26 Jul 2021 23:56:55 +0200 [thread overview]
Message-ID: <20210726235656.1df4ddeb@windsurf> (raw)
In-Reply-To: <20210521140942.3032331-1-giulio.benetti@benettiengineering.com>
On Fri, 21 May 2021 16:09:42 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> This bug has been fixed upstream and backported to buildroot binutils
> package. So let's remove it from toolchain/Config.in and from packages
> that are affected by it:
> - libgeos
> - postgis
> - protobuf
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> V1->V2:
> * squashed 4 different patches into one
> ---
> package/libgeos/Config.in | 4 +---
> package/postgis/Config.in | 4 +---
> package/protobuf/Config.in | 1 -
> toolchain/Config.in | 6 ------
> 4 files changed, 2 insertions(+), 13 deletions(-)
In fact, no I reverted this patch. It depends on other patches to be
applied first. This is an illustration of why you should *never* ever
resend just a single patch out of a larger series. Even if only one
patch is changed, please resend the entire series.
Could you update your "Fix binutils bug 21464 and remove it" series and
resend it?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-26 21:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 14:09 [Buildroot] [PATCH v2] toolchain: remove binutils bug 21464 Giulio Benetti
2021-05-24 4:11 ` Maxim Kochetkov
2021-07-26 21:53 ` Thomas Petazzoni
2021-07-26 21:56 ` Thomas Petazzoni [this message]
2021-07-26 22:03 ` Giulio Benetti
2021-07-26 22:34 ` [Buildroot] [PATCH v2 0/3] Fix binutils bug 21464 and remove it Giulio Benetti
2021-07-26 22:34 ` [Buildroot] [PATCH v2 1/3] package/libgeos: fix build failure due to missing -mcmodel=large Giulio Benetti
2021-07-27 4:26 ` Maxim Kochetkov via buildroot
2021-08-17 20:34 ` Arnout Vandecappelle
2021-08-17 20:56 ` Giulio Benetti
2021-08-17 20:59 ` Arnout Vandecappelle
2021-08-18 20:01 ` Romain Naour
2021-08-18 20:54 ` Giulio Benetti
2021-08-17 21:04 ` Arnout Vandecappelle
2021-07-26 22:34 ` [Buildroot] [PATCH v2 2/3] package/protobuf: " Giulio Benetti
2021-07-27 4:26 ` Maxim Kochetkov
2021-07-26 22:34 ` [Buildroot] [PATCH v2 3/3] toolchain: remove binutils bug 21464 Giulio Benetti
2021-08-17 21:11 ` Arnout Vandecappelle
2021-08-17 21:27 ` Giulio Benetti
2021-12-30 20:05 ` Giulio Benetti
2021-12-30 20:12 ` [Buildroot] [PATCH] package/protobuf: drop dependency on " Giulio Benetti
2021-12-30 20:19 ` Thomas Petazzoni
2021-12-30 20:36 ` [Buildroot] [PATCH v2 3/3] toolchain: remove " Giulio Benetti
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=20210726235656.1df4ddeb@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
--cc=fido_max@inbox.ru \
--cc=giulio.benetti@benettiengineering.com \
--cc=matthew.weber@collins.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.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