diff --git a/8d05288efa59f8bcf1e9230bb4e68e1abceb1268 b/8d05288efa59f8bcf1e9230bb4e68e1abceb1268
index e84b27e..855b9d6 100644
--- a/8d05288efa59f8bcf1e9230bb4e68e1abceb1268
+++ b/8d05288efa59f8bcf1e9230bb4e68e1abceb1268
@@ -246,6 +246,24 @@
       "revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "1a94840b_2cf5a259",
+        "filename": "/PATCHSET_LEVEL",
+        "patchSetId": 1
+      },
+      "lineNbr": 0,
+      "author": {
+        "id": 36731
+      },
+      "writtenOn": "2024-01-29T20:26:35Z",
+      "side": 1,
+      "message": "@mark.asselstine@windriver.com and vefa.bicakci@windriver.com I believe I now more completely understand. In my initial read, I could not trace kernel contexts. The StX kernel has upstream originating from kernel.org and YP and unclear on relative out-of-tree drivers. Per your responses, the StX kernel is sourced from YP which may come with OOT drivers integrated. Thus, they are not OOT as consumed by StX. This was at the heart of what I wanted to trace and now understand and am ok with.\n\nGiven the responses, I am ok with the proposal as written.\n\nI think Mark iterated closer to an associated support question that I originally asked due to my incorrect understanding about YP-related OOT drivers in StarlingX. It\u0027s not quite there but is when expanded, \"the YP community would not be interested in issues raised that would use a modified codebase from what YP produces or non-embedded use cases.\" This does not need to be addressed in this proposal.",
+      "parentUuid": "eedc5aac_d0b76bb8",
+      "revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
     {
       "unresolved": false,
       "key": {