Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Moritz Strübe via buildroot" <buildroot@buildroot.org>
Cc: "Moritz Strübe" <moritz.struebe@siemens-energy.com>
Subject: Re: [Buildroot] [PATCH 1/1] linux: add Linux 6.1 CIP-Kernel
Date: Thu, 9 May 2024 18:16:02 +0200	[thread overview]
Message-ID: <20240509181602.3ce82bb1@windsurf> (raw)
In-Reply-To: <fm-32642-2024042316454638a76fed21d3a8dc75-KB_QAw@errorhandling.siemens-energy.com>

Hello Moritz,

On Tue, 23 Apr 2024 18:45:37 +0200
Moritz Strübe via buildroot <buildroot@buildroot.org> wrote:

> This adds support for the 6.1 CIP-Kernel. As the 5.8 kernel is planned
> to be meaintained until 2023 I added additional options for those
> starting new projects.
> Also update the documentation to reflect the current EOL date instead of
> just stating that it will be meaintained for 10 years.
> 
> Signed-off-by: Moritz Strübe <moritz.struebe@siemens-energy.com>
> ---
>  linux/Config.ext.in |  2 ++
>  linux/Config.in     | 33 +++++++++++++++++++++++++++++----
>  linux/linux.hash    |  2 ++
>  linux/linux.mk      |  2 +-
>  4 files changed, 34 insertions(+), 5 deletions(-)

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?

Thanks a lot for your feedback,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-09 16:16 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 [this message]
2024-07-09 20:29   ` Thomas Petazzoni via buildroot

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=20240509181602.3ce82bb1@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