diff --git a/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 b/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 index 56c4140..2674699 100644 --- a/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 +++ b/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 @@ -193,6 +193,23 @@ "revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268", "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543" }, + { + "unresolved": false, + "key": { + "uuid": "b918bec5_c4805828", + "filename": "/PATCHSET_LEVEL", + "patchSetId": 1 + }, + "lineNbr": 0, + "author": { + "id": 36731 + }, + "writtenOn": "2024-01-26T20:05:34Z", + "side": 1, + "message": "My understanding of the proposal is intends to upgrade StarlingX’s kernel from a Yocto Project (YP) LTS kernel based on a 5.10 kernel.org a YP LTS kernel based on a kernel.org 6.6 kernel. While I completely support and champion adopting a new kernel to take advantage of new features and improve stability, the full picture of this proposal is unclear to me.\n\nThe Storyboard states the upgrade objective is to let StarlingX take advantage of upstream improvements made to the Linux kernel since the release of StarlingX\u0027s current kernel based on v5.10. Bullet two of proposed change states the continued use of the YP kernel as the upstream source for the StarlingX kernel.\n\nAlthough StarlingX’s kernel is sourced from YP, it is unclear how the StarlingX community gets upstream support for its own kernel. Keep in mind that YP originally sources its kernel from kernel.org and doesn’t directly support kernel.org kernel content. I would like the following addressed in the proposal:\n How the StarlingX kernel remediates StarlingX kernel defects where the code \n maintainer is kernel.org, YP, and out-of-tree drivers, respectively.\n\nI did read the relevant uplevel subsection for the StarlingX 6.0 release. Statements made in the subsection were pertinent at the time of the writing. However, progress since the original authoring suggests a different conclusion. I am not advocating that an upstream kernel sourced from Debian be considered for StarlingX 10.0. However, I do suggest that there be an update somewhere in the StarlingX ethos that revisits the topic and that the 6.0 uplevel analysis reference be removed from this, specific proposal.\n\nIf out-of-tree is relative to any other kernel besides YP, please reference the kernel. For example, “YP out-of-tree” and “StX out-of-tree” to be clear on where technical debt is being applied.", + "revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268", + "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543" + }, { "unresolved": false, "key": {