From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Supported kernel and Debian versions in Isar
Date: Fri, 12 Apr 2019 12:39:36 +0100 [thread overview]
Message-ID: <1555069176.3557.17.camel@codethink.co.uk> (raw)
In-Reply-To: <OSBPR01MB27743E33CB9ED2B9B5885577E12F0@OSBPR01MB2774.jpnprd01.prod.outlook.com>
On Thu, 2019-04-11 at 08:33 +0000, kazuhiro3.hayashi at toshiba.co.jp wrote:
[...]
> Do you any plans to provide the kernel recipes for all CIP versions (4.4, 4.19, ...) in master branch
> and validate them with all Debian versions?
> I guess that the supported combinations would be limited to practical ones.
> For examples:
> 4.4 + stretch => SUPPORTED
> 4.4 + buster => NOT SUPPORTED
> 4.4 + bullseye => NOT SUPPORTED
That makes sense to me.
> 4.19 + stretch => SUPPORTED
> 4.19 + buster => NOT SUPPORTED
That should be supported as Debian's official kernel packages for
buster are based on 4.19.
> 4.19 + bullseye => SUPPORTED(?)
[...]
That should be supportable - Debian generally tries to support partial
upgrades including upgrading all of userland without the kernel, so
bullseye userland should be compatible with 4.19.
Ben.
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next prev parent reply other threads:[~2019-04-12 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 8:33 [cip-dev] Supported kernel and Debian versions in Isar kazuhiro3.hayashi at toshiba.co.jp
2019-04-11 8:36 ` kazuhiro3.hayashi at toshiba.co.jp
2019-04-11 9:01 ` Jan Kiszka
2019-04-11 11:39 ` kazuhiro3.hayashi at toshiba.co.jp
2019-04-11 12:15 ` Jan Kiszka
2019-04-12 6:05 ` kazuhiro3.hayashi at toshiba.co.jp
2019-04-12 11:28 ` Jan Kiszka
2019-04-16 9:08 ` kazuhiro3.hayashi at toshiba.co.jp
2019-04-12 11:39 ` Ben Hutchings [this message]
2019-04-16 9:20 ` kazuhiro3.hayashi at toshiba.co.jp
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=1555069176.3557.17.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.