From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Florian Larysch <fl@n621.de>
Cc: buildroot@buildroot.org, Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH 1/1] package/go: security bump to version 1.27.3
Date: Tue, 20 Oct 2026 16:04:18 +0200 [thread overview]
Message-ID: <atd03lI9AqiO72jJ@windsurf> (raw)
In-Reply-To: <20261020131404.7333-2-fl@n621.de>
On Tue, Oct 20, 2026 at 03:13:58PM +0200, Florian Larysch wrote:
> https://go.dev/doc/devel/release#go1.27.3
> https://groups.google.com/g/golang-announce/c/66pojueaQek/m/tmWX2Pq9AgAJ
>
> Fixes CVE-2026-111943.
>
> Signed-off-by: Florian Larysch <fl@n621.de>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
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
prev parent reply other threads:[~2026-10-20 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 13:13 [Buildroot] [PATCH 1/1] package/go: security bump to version 1.27.3 Florian Larysch
2026-10-20 14:04 ` Thomas Petazzoni via buildroot [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=atd03lI9AqiO72jJ@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=fl@n621.de \
--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