14642 2021-12-03 17:44:40 +0000 Yocto-check-layer add patch Upstream-Status check 2023-03-14 08:20:17 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools unspecified x86 Multiple RESOLVED FIXED Medium+ enhancement 4.2 M3 1 akuster808 chee.yang.lee chee.yang.lee mingli.yu randy.macleod richard.purdie ross.burton --- --- Don't know oldest_to_newest 92088 0 akuster808 2021-12-03 17:44:40 +0000 92091 1 richard.purdie 2021-12-05 12:33:01 +0000 Should the compatibility status mandate some percentage of patches are not in Pending state? The later checks could at least report the percentage of patches in pending state? 92143 2 akuster808 2021-12-11 13:59:27 +0000 (In reply to comment #1) > Should the compatibility status mandate some percentage of patches are not > in Pending state? The later checks could at least report the percentage of > patches in pending state? I hadn't thought to that level of details. yes, I think a percent of patches with no 'Upsteam-Status" and with status may be a good first step. I am not sure about mandating a percentage. I am thinking of a BSP layer with an EOL kernel having patches that have no where to go but a form of the patch may have been accepted in a later. I think its more important to have the data to allow a deep dive into the areas of concern. 92182 3 akuster808 2021-12-16 15:58:07 +0000 Having an "Upstream-Status" in patches is being considered an additional Yocto Compatible requirement. 95018 4 chee.yang.lee 2023-02-27 06:56:44 +0000 This added check for Upstream-Status. https://git.yoctoproject.org/poky/commit/?id=80a2028813d3c861f3aea0d7f5e91d9cccb7d689 95126 5 richard.purdie 2023-03-14 08:20:17 +0000 Since we now show the warnings in yocto-check-layer, I think we can resolve this, thanks for the patch!