diff options
author | David S. Miller <davem@davemloft.net> | 2016-10-04 02:11:58 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-10-04 02:11:58 -0400 |
commit | 9a8dd213d2a38349e5ea2ca8888400952112b45c (patch) | |
tree | 02f0909f72e3bcae754d8e22e2dcc6c5d8878359 /include/uapi/linux/pkt_cls.h | |
parent | 93409033ae653f1c9a949202fb537ab095b2092f (diff) | |
parent | 2c15f25b2923435515298589dcaa2eace6a948c1 (diff) |
Merge branch 'ncsi-next'
Gavin Shan says:
====================
net/ncsi: NCSI Improvment and bug fixes
This series of patches improves NCSI stack according to the comments
I received after the NCSI code was merged to 4.8.rc1:
* PATCH[1/8] fixes the build warning caused by xchg() with ia64-linux-gcc.
The atomic operations are removed. The NCSI's lock should be taken when
reading or updating its state and chained state.
* Channel ID (0x1f) is the reserved one and it cannot be valid channel ID.
So we needn't try to probe channel whose ID is 0x1f. PATCH[2/8] and
PATCH[3/8] are addressing this issue.
* The request IDs are assigned in round-robin fashion, but it's broken.
PATCH[4/8] make it work.
* PATCH[5/8] and PATCH[6/8] reworks the channel monitoring to improve the
code readability and its robustness.
* PATCH[7/8] and PATCH[8/8] introduces ncsi_stop_dev() so that the network
device can be closed and opened afterwards. No error will be seen.
Changelog
=========
v2:
* The NCSI's lock is taken when reading or updating its state as the
{READ,WRITE}_ONCE() isn't reliable.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/uapi/linux/pkt_cls.h')
0 files changed, 0 insertions, 0 deletions