Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Buildroot List <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [PATCH 3/3] package/binutils: drop version 2.32
Date: Tue, 26 Apr 2022 17:44:05 +0200	[thread overview]
Message-ID: <20220426174405.09a8825a@windsurf> (raw)
In-Reply-To: <20220426153726.312870-3-thomas.petazzoni@bootlin.com>

On Tue, 26 Apr 2022 17:37:25 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> Now that recent versions of binutils work with FLAT binaries, we can
> drop the old 2.32 version, which was kept only to keep support FLAT
> binaries.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Sorry, I forgot to drop the hash in binutils.hash on this one. I can
resend a v2 if needed.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-26 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 15:37 [Buildroot] [PATCH 1/3] package/elf2flt: update to version 2021.08 Thomas Petazzoni via buildroot
2022-04-26 15:37 ` [Buildroot] [PATCH 2/3] package/binutils: re-enable recent versions of binutils for FLAT binaries Thomas Petazzoni via buildroot
2022-04-26 15:37 ` [Buildroot] [PATCH 3/3] package/binutils: drop version 2.32 Thomas Petazzoni via buildroot
2022-04-26 15:44   ` Thomas Petazzoni via buildroot [this message]
2022-04-26 17:14 ` [Buildroot] [PATCH 1/3] package/elf2flt: update to version 2021.08 Baruch Siach via buildroot

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=20220426174405.09a8825a@windsurf \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.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