From: David Howells
Date: Thu, 09 Jun 2016 23:02:51 +0100
> Simplify the RxRPC connect() implementation. It will just note the
> destination address it is given, and if a sendmsg() comes along with no
> address, this will be assigned as the address. No transport struct
From: David Howells
Date: Thu, 09 Jun 2016 23:02:51 +0100
> Simplify the RxRPC connect() implementation. It will just note the
> destination address it is given, and if a sendmsg() comes along with no
> address, this will be assigned as the address. No transport struct will be
> held
Can you take this into net/next please?
Thanks,
David
Can you take this into net/next please?
Thanks,
David
Simplify the RxRPC connect() implementation. It will just note the
destination address it is given, and if a sendmsg() comes along with no
address, this will be assigned as the address. No transport struct will be
held internally, which will allow us to remove this later.
Simplify sendmsg()
Simplify the RxRPC connect() implementation. It will just note the
destination address it is given, and if a sendmsg() comes along with no
address, this will be assigned as the address. No transport struct will be
held internally, which will allow us to remove this later.
Simplify sendmsg()
.
The other significant UAPI change is that I deal better with a race between
two threads trying to register calls with the same user ID (one of them
will get an error).
David
---
rxrpc: Simplify connect() implementation and simplify sendmsg() op
Simplify the RxRPC connect() implementation. It will just
.
The other significant UAPI change is that I deal better with a race between
two threads trying to register calls with the same user ID (one of them
will get an error).
David
---
rxrpc: Simplify connect() implementation and simplify sendmsg() op
Simplify the RxRPC connect() implementation. It will just
8 matches
Mail list logo