From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] {linux, linux-headers}: bump 7.2.x, 6.18.x, 6.12.x, 6.6.x series
Date: Wed, 21 Oct 2026 20:55:33 +0200 [thread overview]
Message-ID: <atkKodWLRXWa1jy1@windsurf> (raw)
In-Reply-To: <20261021171000.3332724-1-fiona.klute@gmx.de>
On Wed, Oct 21, 2026 at 07:10:00PM +0200, Fiona Klute via buildroot wrote:
> Update the latest kernel releases to:
> - 7.2.11 -> 7.2.12
> - 6.18.57 -> 6.18.58
> - 6.12.113 -> 6.12.114
> - 6.6.159 -> 6.6.160
>
> Signed-off-by: Fiona Klute <fiona.klute@gmx.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-21 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 17:10 [Buildroot] [PATCH 1/1] {linux, linux-headers}: bump 7.2.x, 6.18.x, 6.12.x, 6.6.x series Fiona Klute via buildroot
2026-10-21 18:55 ` 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=atkKodWLRXWa1jy1@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.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