On 4/16/22 17:50, Richard Purdie wrote:

On Sat, 2022-04-16 at 17:48 +0800, Robert Yang wrote:

Thank you very much, I'm trying to run the test cases, but I found that you've
already fixed them, thanks again.

I don't know why it was set to proprietary in the test but it doesn't seem to
cause any regressions so I removed it. It is at an older version which should
mean it doesn't affect other builds so I'm happy to leave it on the older
version.

The following supported versions have the same problem, should we also fix them?

Dunfell
Hardknott
Honister

I'd like to send the patches after testing if we need fix them.