On Fri, Jun 16, 2017 at 9:46 AM, Luis R. Rodriguez <mcg...@kernel.org> wrote:
>> 47e0bbb7fa98 (test: firmware_class: report errors properly on failure)
>
> Hrm, come to think of it, this *might* have been a stable fix, however the
> fix did not mention any specific about real issue with this. Kees?

This was mostly a cosmetic fix, though it does fix the return code. It
can certainly go to stable, but I try to only push more critical
things to -stable.

-Kees

-- 
Kees Cook
Pixel Security

Reply via email to