> I don't understand why you want to force a valid pointer here. According > to my sense of defensive programming I'd say: If the bus driver doesn't > expect the slave to consume/provide a value, let's pass NULL to notice > the assumption being wrong. The wording is fine, now. For me, an OOPS is quite much of a "notice". I assume there will be non-upstream backends. I am not keen to see devices in the field to OOPS because the implementation missed a case how to handle the pointer correctly. Now, the rule of thumb is easy: Always pass the pointer.
Attachment:
signature.asc
Description: Digital signature
