From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: "Moritz Strübe" <moritz.struebe@siemens-energy.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] linux: add Linux 6.1 CIP-Kernel
Date: Tue, 9 Jul 2024 22:29:51 +0200 [thread overview]
Message-ID: <20240709222951.74066a4e@windsurf> (raw)
In-Reply-To: <20240509181602.3ce82bb1@windsurf>
Hello,
On Thu, 9 May 2024 18:16:02 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> Thanks for the patch. My question is what does the CIP 6.1 kernel
> brings that the "official stable 6.1" doesn't bring? Indeed official
> 6.1 is still maintained by GKH until Dec 2026. I do understand the
> value of CIP when it picks up maintenance after the "main" kernel
> community gives up, but for something still maintained?
>
> This question in fact also applies to the current CIP 5.10 kernel we
> already have, as 5.10 is still maintained upstream, also until Dec 2026.
>
> Wouldn't it make more sense to have the CIP 4.4 kernel in Buildroot,
> for which there is no longer any maintenance upstream, and therefore
> for which the CIP effort does make sense?
Since no feedback was provided to this question, I marked the patch as
Rejected. We can of course revisit if additional feedback/argumentation
is provided, for sure!
Best regards,
Thomas
--
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:[~2024-07-09 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 16:45 [Buildroot] [PATCH 1/1] linux: add Linux 6.1 CIP-Kernel Moritz Strübe via buildroot
2024-05-09 16:16 ` Thomas Petazzoni via buildroot
2024-07-09 20:29 ` 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=20240709222951.74066a4e@windsurf \
--to=buildroot@buildroot.org \
--cc=moritz.struebe@siemens-energy.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