Had a quick look at this during a patch-pilot shift -- the patch is simple enough, and the test plan looks reasonable, but it only covers the system *after* the proposed version is installed. Ideally, the test plan should re-produce the bug (with the released version of vision- drivers), have the user install the proposed version and re-test to show that this change (and only this change) fixes the issue (as opposed to anything random in the background like other upgrades).
In other words, the test plan is *almost* complete but could do with one additional step at the top, for example, to visit https://webcamtests.com and show that the privacy LED does not light. The section on where problems could occur needs more detail: it mentions that an error is reported in dmesg. Does that apply to the affect platforms only, or to other platforms? The mere fact an error is reported in dmesg may cause other issues in itself. Furthermore, just because this is fixing an initialization value only, does not make it any less likely that the fix may have knock-on effects. The SRU team are rather likely to pick up on this section as not having enough detail currently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2106807 Title: Privacy LED may not be turned on on OEM Renegade platform with Intel IPU7 camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2106807/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
