> &error_warn? :) But then, /machine/rtc.tm is the only supported interface,
I have thought about &error_warn in the past, but thought the better
of it. Warnings need user digestable message and I can't think of a
sane implementation where you populate a message for error framework
to raise while maintaining the needed errp == NULL || *errp == NULL
semantic at the same time.
> and it should be the same for all RTC devices so perhaps a NULL error
> pointer is enough.
>
NULL Works for me. But other than source verbosity is there any reason
to not catch the error?: