From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{14, 19}.x / 5.{4, 10, 15}.x / 6.{1, 6}.x series
Date: Sun, 14 Jan 2024 17:37:03 +0100 [thread overview]
Message-ID: <871qajna6o.fsf@48ers.dk> (raw)
In-Reply-To: <20240113162647.3316051-1-bernd@kuhls.net> (Bernd Kuhls's message of "Sat, 13 Jan 2024 17:26:44 +0100")
>>>>> "Bernd" == Bernd Kuhls <bernd@kuhls.net> writes:
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Committed to 2023.02.x and 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-01-14 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 16:26 [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{14, 19}.x / 5.{4, 10, 15}.x / 6.{1, 6}.x series Bernd Kuhls
2024-01-13 16:26 ` [Buildroot] [PATCH 2/4] {toolchain, linux-headers}: add support for 6.7 headers Bernd Kuhls
2024-01-13 16:26 ` [Buildroot] [PATCH 3/4] linux: bump latest version to 6.7 Bernd Kuhls
2024-01-13 20:42 ` Peter Korsgaard
2024-01-13 16:26 ` [Buildroot] [PATCH 4/4] package/linux-headers: drop 4.14.x option Bernd Kuhls
2024-01-13 20:42 ` Peter Korsgaard
2024-01-13 20:41 ` [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{14, 19}.x / 5.{4, 10, 15}.x / 6.{1, 6}.x series Peter Korsgaard
2024-01-14 16:36 ` Peter Korsgaard
2024-01-14 16:37 ` Peter Korsgaard [this message]
[not found] ` <875xzvna6v.fsf__46587.6769552537$1705250246$gmane$org@48ers.dk>
2024-01-14 16:58 ` Bernd Kuhls
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=871qajna6o.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.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