Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/binutils: add version 2.39
Date: Thu, 11 Aug 2022 22:26:02 +0200	[thread overview]
Message-ID: <20220811222602.1406c56d@windsurf> (raw)
In-Reply-To: <YvTr2e/Y0o128SWs@waldemar-brodkorb.de>

On Thu, 11 Aug 2022 13:45:29 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> Patch 0002-poison-system-directories.patch got rebased.
> Patch 0004+0005 is upstreamed and got removed.
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
>  package/binutils/2.39/0001-sh-conf.patch      |  48 +++
>  .../2.39/0002-poison-system-directories.patch | 298 ++++++++++++++++++
>  ...or1k-fix-building-with-gcc-version-5.patch |  50 +++
>  package/binutils/Config.in.host               |   4 +
>  package/binutils/binutils.hash                |   1 +
>  5 files changed, 401 insertions(+)
>  create mode 100644 package/binutils/2.39/0001-sh-conf.patch
>  create mode 100644 package/binutils/2.39/0002-poison-system-directories.patch
>  create mode 100644 package/binutils/2.39/0003-bfd-elf32-or1k-fix-building-with-gcc-version-5.patch

Thanks for this patch series! We will keep this for 2022.11, so we will
merge this to next once 2022.08-rc1 is released.

Thanks!

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-08-11 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 11:45 [Buildroot] [PATCH 1/2] package/binutils: add version 2.39 Waldemar Brodkorb
2022-08-11 20:26 ` Thomas Petazzoni via buildroot [this message]
2022-08-12 22:16 ` Thomas Petazzoni 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=20220811222602.1406c56d@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@openadk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox