On 07/08/17 12:25, Arend van Spriel wrote: > On 26-07-17 22:25, Ian Molton wrote: >> Register access code is not the place for band-aid fixes like this. >> If this is a genuine problem, it should be fixed further up in the driver >> stack. > > So lets make it a SDIO debug message for all register accesses getting > rid of the error message.
Not quite sure I follow here - but as the code is completely gone in later patches in the series, does it matter? Perhaps address this if it in future, if it crops up as a problem, since it wont be fatal even if it does... -Ian
