Re: [PATCH net-next v2 0/5] bonding: groundwork and initial conversion to RCU

[PATCH net-next v2 0/5] bonding: groundwork and initial conversion to RCU · Nikolay Aleksandrov <hidden> · 2013-08-01
[PATCH net-next v2 1/5] bonding: convert to list API and replace bond's custom list · Nikolay Aleksandrov <hidden> · 2013-08-01
[PATCH net-next v2 4/5] bonding: factor out slave id tx code and simplify xmit paths · Nikolay Aleksandrov <hidden> · 2013-08-01
[PATCH net-next v2 5/5] bonding: initial RCU conversion · Nikolay Aleksandrov <hidden> · 2013-08-01
[PATCH net-next v2 2/5] bonding: remove unnecessary read_locks of curr_slave_lock · Nikolay Aleksandrov <hidden> · 2013-08-01
[PATCH net-next v2 3/5] bonding: simplify broadcast_xmit function · Nikolay Aleksandrov <hidden> · 2013-08-01
Re: [PATCH net-next v2 0/5] bonding: groundwork and initial conversion to RCU · Nikolay Aleksandrov <hidden> · 2013-08-01

From: Nikolay Aleksandrov <hidden>
Date: 2013-08-01 13:17:46

Self-nack, sorry for the noise but I found a problem with the new 3ad code, we
need to check if the list has been traversed when extracting the next port.

v3 will follow after I run some more tests.

Nik

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help