Hi Marcel,
can we please have a proper thread on what error is appropriate to send > from a socket interface when this situation happens. I see that
> we are flipping errors, but my request to discuss this gets ignored.
I already gave my opinion previously. Let's recall it :"About the error
ECONNABORTED, it is what the patch does : abort a connection. It is not
used for other purposes. If you really want to change, I'm ok with
EOPNOTSUPP, otherwise please suggest."
Regarding EOPNOTSUPP. Most use case are when a pointer in an interface
is not implemented. We could consider that SetupSyncConn is not
implemented in 2.0 adapter interfaces.
> Please look for a good reference of the error code usage in other
socket protocols or manpages
It is not obvious to find one good reference. But for example there is :
Documentation/ioctl/hdio.txt: EOPNOTSUPP Hardware interface does
not support bus power
Another option could be:
[ENODEV]
No such device An attempt was made to apply an inappropriate
function to a device; for example, trying to read a write-only device
such as a printer.
BR,
Fred
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
