From 3043e272017355458e4319d67985430dce890a6f Mon Sep 17 00:00:00 2001 From: Gerrit User 33377 <33377@4a232e18-c5a9-48ee-94c0-e04e7cca6543> Date: Fri, 26 Jan 2024 21:15:20 +0000 Subject: [PATCH] Update patch set 1 Patch Set 1: (1 comment) Patch-set: 1 Attention: {"person_ident":"Gerrit User 36731 \u003c36731@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_33377\u003e replied on the change"} Attention: {"person_ident":"Gerrit User 33377 \u003c33377@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_33377\u003e replied on the change"} --- 8d05288efa59f8bcf1e9230bb4e68e1abceb1268 | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 b/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 index 2674699..aa9766a 100644 --- a/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 +++ b/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 @@ -210,6 +210,24 @@ "revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268", "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543" }, + { + "unresolved": true, + "key": { + "uuid": "46484339_fc578fe1", + "filename": "/PATCHSET_LEVEL", + "patchSetId": 1 + }, + "lineNbr": 0, + "author": { + "id": 33377 + }, + "writtenOn": "2024-01-26T21:15:20Z", + "side": 1, + "message": "Hi Steve,\n\nThank you for the feedback!\n\nI need to admit most of the topics you mention are beyond my vision and/or knowledge as a StarlingX contributor who happens to be employed by Wind River. I will consult with other colleagues, I will try to address your feedback with a newer revision of the specification proposal.\n\nIn the meantime, if you could clarify what you meant by (or what you were referring to with) \"However, progress since the original authoring suggests a different conclusion\", I would really appreciate it.\n\nA few notes:\n\n---\n\n\u003e Although 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.\n\nI hope that I did not misunderstand, but I feel as if this is not directly within the scope of this proposal, as this proposal itself does not change the pre-existing support structure. Upstream support for the Linux kernel is, I am afraid, on a best-effort basis for members of projects like StarlingX.\n\nStarlingX community members can isolate bugs they find in the StarlingX kernel to a few different sources: StarlingX\u0027s own kernel patches layered on top of linux-yocto and linux-yocto\u0027s patches layered on top of kernel.org, and then kernel.org sources. (We can also consider the PREEMPT_RT patches inherited from linux-yocto, utilized in the low-latency StarlingX kernel, a separate \"layer\".)\n\nIf a StarlingX-specific kernel patch is found to be the culprit for an issue, then the bug should be reported on the StarlingX bug tracker on launchpad.net. That is the main support mechanism of the StarlingX community in addition to the mailing list and Matrix channels, as far as I know.\n\nIn contrast, if a bug is isolated into linux-yocto or kernel.org-specific upstream changes, then, **in addition** to the StarlingX bug tracker, **willing** community members may opt to report their findings on relevant mailing lists (such as linux-yocto@lists.yoctoproject.org for linux-yocto, and linux-kernel@vger.kernel.org and other appropriate mailing lists for kernel.org-maintained code).\n\nFollowing that bug report, fixing the actual issue is mostly a volunteer effort from the Linux kernel development community. (StarlingX does not have influence on this, as far as I know.) kernel.org\u0027s issue reporting and resolution process is discussed in depth here: https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html\n\nIf anyone in the StarlingX community has a need for paid/non-volunteer support, then there are companies like Wind River that can provide support and maintenance contracts.\n\nI apologize, as I am under the impression that what I stated above is already obvious to you. I believe that I need clarification regarding your ask.\n\n---\n\n\u003e How the StarlingX kernel remediates StarlingX kernel defects where the code maintainer is kernel.org, YP, and out-of-tree drivers, respectively\n\nMy current understanding is that Wind River is currently (and has been) a major contributor to StarlingX, and hence resolves most of the bugs and handles the maintenance of the StarlingX kernel and in-tree and out-of-tree device drivers shipped with StarlingX.\n\nResolving kernel issues usually involves StarlingX-specific patches, which most of the time are cherry-picks of upstream kernel.org commits. Occasionally, bugs in some of the out-of-tree drivers are fixed by the vendors providing the drivers, by releasing newer/fixed versions of the drivers, which are then pulled into StarlingX.\n\nI would like to note again that this proposal does not propose changing the aforementioned pre-existing support structure for the fixing of kernel and/or out-of-tree driver bugs.\n\n---\n\n\u003e \"If 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.\"\n\nIn the Linux kernel community, the term \"out-of-tree\" is commonly used for drivers that are not included in the mainline kernel tree released by kernel.org.\n\nMy understanding is that the linux-yocto does not include drivers additional to what kernel.org kernels provide **in the linux-yocto branches utilized by StarlingX**: vX.Y/standard/base and vX.Y/standard/preempt-rt/base.\n\nAll this to say, by out-of-tree drivers, the document was referring to the drivers in the following listing: https://opendev.org/starlingx/kernel/src/branch/master/kernel-modules\n\nThese drivers are added to StarlingX by the StarlingX community, so based on your terminology, they would constitute \"StarlingX out-of-tree\", I think. Please correct me if my understanding is wrong.\n\nIf it would be beneficial, I can clarify the meaning of \"out-of-tree\" in the next revision of this commit.\n\n---\n\nFinally, I would like to state that I am only expressing my personal understanding regarding StarlingX, Yocto Project and kernel.org-related projects. I am **not** speaking for my employer, Wind River.\n\nAgain, I would really appreciate any and all clarification you can provide regarding your asks, based on what I wrote above.\n\nThanks!\n\nVefa\n\n(I am marking this as un-resolved, as addressing these feedback items will require a revision of the specification proposal.)", + "parentUuid": "b918bec5_c4805828", + "revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268", + "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543" + }, { "unresolved": false, "key": {