On 05.12.20 22:23, Marc Kleine-Budde wrote:
On 12/5/20 10:15 PM, Oliver Hartkopp wrote:
On 04.12.20 14:55, Thomseeen wrote:
EADDRNOTAVAIL shouldn't be thrown when an invalid RX address (e.g. NO_CAN_ID)
is set while the socket is used with the CAN_ISOTP_SF_BROADCAST flag.
Signed-off-by: Thomseeen <thwa1@xxxxxx>
Acked-by: Oliver Hartkopp <socketcan@xxxxxxxxxxxx>
Should this be squashed into "support for functional addressing"?
Can you re-post the two or three isotp patches, as they should go into
can-next/net-next?
Yes, will do.
98bef9295d07 can: isotp: isotp_setsockopt(): block setsockopt on bound sockets
21f10f1b5c3a can: isotp: add SF_BROADCAST support for functional addressing
Marc
