diff options
author | David S. Miller <davem@davemloft.net> | 2016-04-11 22:34:42 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-04-11 22:34:42 +0300 |
commit | 7c3da7d0d4f3506ef70d9cf148a22400477854d0 (patch) | |
tree | 717c4bd8d4a001016917688b38ce767ecf79ce39 /drivers/pwm/pwm-mxs.c | |
parent | c64a73d584cc344915baee1183c791c0d0c42d79 (diff) | |
parent | e0e4d82f3be60cfe8b10304c6daf3ca5973ae9e3 (diff) | |
download | linux-7c3da7d0d4f3506ef70d9cf148a22400477854d0.tar.xz |
Merge branch 'rprpc-2nd-rewrite-part-1'
David Howells says:
====================
RxRPC: 2nd rewrite part 1
Okay, I'm in the process of rewriting the RxRPC rewrite. The primary aim of
this second rewrite is to strictly control the number of active connections we
know about and to get rid of connections we don't need much more quickly.
On top of this, there are fixes to the protocol handling which will all occur
in later parts.
Here's the first set of patches from the second go, aimed at net-next. These
are all fixes and cleanups preparatory to the main event.
Notable parts of this set include:
(1) A fix for the AFS filesystem to wait for outstanding calls to complete
before closing the RxRPC socket.
(2) Differentiation of local and remote abort codes. At a future point
userspace will get to see this via control message data on recvmsg().
(3) Absorb the rxkad module into the af_rxrpc module to prevent a dependency
loop.
(4) Create a null security module and unconditionalise calls into the
security module that's in force (there will always be a security module
applied to a connection, even if it's just the null one).
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/pwm/pwm-mxs.c')
0 files changed, 0 insertions, 0 deletions