Hi Partha, I suggest you should resend the series as well as its dependency when Jon Maloy's "[PATCH net-next v7 0/4] tipc: neighbor monitoring etc" was merged into upstream.
Regards, Ying -----Original Message----- From: Parthasarathy Bhuvaragan [mailto:parthasarathy.bhuvara...@ericsson.com] Sent: 2016年6月2日 22:10 To: tipc-discussion@lists.sourceforge.net; jon.ma...@ericsson.com; ma...@donjonn.com; Xue, Ying; richard.a...@ericsson.com Subject: [PATCH iproute2 v3 00/10] tipc: updates for neighbour monitor This commit series requires the following kernel patch set: "[PATCH net-next v2 0/5] tipc: netlink updates for neighbour monitor" v3: - simplified the header layouts in commit#9. - updated man pages. v2: - split patches into self-contained complete commits. - address review comments from richard alpe. - cleanup of tipc bearer. - introduce tipc link monitor summary Note: 1. I have issues compiling the latest iproute2 package, so compiled on commit c13b6b097ab3 "add coverity model file". 2. This series conflicts with: "[PATCH iproute2 0/4] introduce bearer get and bearer add". needs rebase when submiting to net-next. regards Partha Parthasarathy Bhuvaragan (10): tipc: remove dead code tipc: introduce cmd_get_unique_bearer_name() function tipc: validate bearer arguments early tipc: fix bearer operations with media=ib tipc: add link monitor set threshold tipc: add link monitor get threshold tipc: add link monitor summary tipc: export some bearer helper functions tipc: add link monitor list tipc: update man page for link monitor include/linux/tipc_netlink.h | 37 ++++ man/man8/tipc-link.8 | 101 +++++++++++ tipc/bearer.c | 412 ++++++++++++++++++++++++------------------- tipc/bearer.h | 3 + tipc/link.c | 376 ++++++++++++++++++++++++++++++++++++++- 5 files changed, 744 insertions(+), 185 deletions(-) -- 2.1.4 ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion