Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>
Cc: yann.morin@orange.com, ibai.erkiaga-elorza@amd.com,
	luca.ceresoli@bootlin.com, buildroot@buildroot.org,
	brandon.maier@collins.com, ju.o@free.fr,
	thomas.petazzoni@bootlin.com, romain.naour@smile.fr,
	michal.simek@amd.com, romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v3 1/1] package/gcc-bare-metal: bump to gcc 16.1.0
Date: Sat, 13 Jun 2026 22:35:34 +0200	[thread overview]
Message-ID: <87v7bmnppl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260604102140.3252257-1-neal.frager@amd.com> (Neal Frager's message of "Thu, 4 Jun 2026 11:21:40 +0100")

>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:

 > Bump gcc-bare-metal to gcc 16.1.0.
 > 0001-libcody-Make-it-buildable-by-C-11-to-C-26.patch is already included in
 > gcc 16.1.0, so this patch can be removed.

 > See here for changes:
 > https://gcc.gnu.org/gcc-16/changes.html

 > Signed-off-by: Neal Frager <neal.frager@amd.com>
 > ---
 > V1-> V2:
 > - remove 0001-libcody-Make-it-buildable-by-C-11-to-C-26.patch as it is already
 >   included with gcc 16.1.0
 > V2-> V3:
 > - updated comment about where the sha512.sum is coming from in
 >   gcc-bare-metal.hash

Committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-06-13 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 10:21 [Buildroot] [PATCH v3 1/1] package/gcc-bare-metal: bump to gcc 16.1.0 Neal Frager via buildroot
2026-06-13 20:35 ` 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=87v7bmnppl.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=brandon.maier@collins.com \
    --cc=buildroot@buildroot.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=ju.o@free.fr \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michal.simek@amd.com \
    --cc=neal.frager@amd.com \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin@orange.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