Hi Alex and Bjorn,
[...]
> > This changes the attribute contents from "(null)" to an empty
> > (zero-length) file when no driver override has been set.
> >
> > There are a few other driver_override_show() functions. Most don't
> > check the pointer so they'll show "(null)". One (spi.c) checks and
> > shows an empty string ("", file containing a single NULL character)
> > instead of an empty (zero-length) file.
>
> Yeah, "(null)" was the expected output in this case. It looks like
> this might break driverctl. Thanks,
[...]
I had a look and it does, indeed, rely on explicitly checking whether
the value is "(null)", as per:
https://gitlab.com/driverctl/driverctl/-/blob/master/driverctl#L96-131
I think, to avoid breaking this and other userspace tools that might
rely on this, we should drop this patch.
Having said that, I would love to be able to correct the behaviour we
have at the moment, but it seems that this ship has sail, so to speak.
Krzysztof
