2 Dec
2019
2 Dec
'19
9:21 p.m.
On Mon, Dec 02, 2019 at 06:34:14PM +0100, Christoph Hellwig wrote:
Yes. I guess your patch is the best thing for now:
Reviewed-by: Christoph Hellwig hch@lst.de
Thanks, applied for-5.5
But I think we might need a new kernel tain flag or something like it for devices that are so obviously broken in their identifiers.
That's fine with me. We currently just log a warning when an error is returned here, we can add_taint() too. Which flag do you think? TAINT_FIRMWARE_WORKAROUND, TAINT_CRAP, or something else?