Stanislaw Gruszka <stf_xl@xxxxx> wrote:
> As reported by Exuvo is possible that we have lot's of EPROTO errors
> during device start i.e. firmware load. But after that device works
> correctly. Hence marking device gone by few EPROTO errors done by
> commit e383c70474db ("rt2x00: check number of EPROTO errors") caused
> regression - Exuvo device stop working after kernel update. To fix
> disable the check during device start.
>
> Link: https://lore.kernel.org/linux-wireless/bff7d309-a816-6a75-51b6-5928ef4f7a8c@xxxxxxxx/
> Reported-and-tested-by: Exuvo <exuvo@xxxxxxxx>
> Fixes: e383c70474db ("rt2x00: check number of EPROTO errors")
> Cc: stable@xxxxxxxxxxxxxxx
> Signed-off-by: Stanislaw Gruszka <stf_xl@xxxxx>
Patch applied to wireless-drivers.git, thanks.
ed53ae756930 rt2x00: do not mark device gone on EPROTO errors during start
--
https://patchwork.kernel.org/project/linux-wireless/patch/20211111141003.GA134627@xxxxx/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
