From: "Luca Weiss" <luca.weiss@fairphone.com>
To: <cip-dev@lists.cip-project.org>
Cc: <karsten@fairphone.com>
Subject: Questions about SLTS v4.19
Date: Wed, 22 Jan 2025 10:16:52 +0100 [thread overview]
Message-ID: <D78HLVUGEZ2B.19ENWIOOSFW5A@fairphone.com> (raw)
Hi,
I've got some questions regarding the SLTS v4.19 tree which I couldn't
find an answer to on the website.
As Fairphone, one of our Android devices, Fairphone 4 is running on a
4.19 kernel fork which was provided by Qualcomm. Unfortunately
linux-stable support has run out and while we're looking into upgrading
the kernel to a newer version, for now we're stuck with 4.19.
Since CIP will continue maintaining the 4.19 kernel for the foreseeable
future, we were thinking about starting to merge the v4.19 CIP releases
into our tree, and continuing to do that for the foreseable future.
But it's not clear to me what is actually in scope for the 4.19 branch.
At
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
I see the text "For the 4.4 branch, the architectures we've committed to
so far are arm (32-bit) and x86_64." but no info about 4.19, whether
arm64 will be included, which is what our device is running on.
And also while we're not a CIP member we'd like to know whether we can
consider the CIP branches to be reasonably equivalent to the
linux-stable branches, for example where we can assume that all known
(security) issues will be getting the fixes backported, or how else it
might differ from regular LTS.
Regards
Luca
next reply other threads:[~2025-01-23 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 9:16 Luca Weiss [this message]
2025-01-25 6:34 ` Questions about SLTS v4.19 Jan Kiszka
2025-01-31 11:59 ` [cip-dev] " Pavel Machek
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=D78HLVUGEZ2B.19ENWIOOSFW5A@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=cip-dev@lists.cip-project.org \
--cc=karsten@fairphone.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