Hi Ying, Thanks for the information. I will follow this while submitting to "net-next".
For this series, I might have to wait and see david's response as its tagged as "Under Review". regards Partha On 07/23/2016 12:06 PM, Xue, Ying wrote: > Hi Parthasarathy, > > I don't think this might be a proper time to submit the series to "net-next" > tree. As kernel mainline version goes to 4.7-rc7, it means that "net-next" > tree has already entered into merge window. So I guess when the "net-next" is > open, you need to resubmit the series again. > In general, we don't encourage to submit patches to net-next tree when the > version of kernel mainline runs to RC6 and later except that there are some > urgent features/fixes we really want to merge into mainline tree during this > window. > > Regards, > Ying > > -----Original Message----- > From: Parthasarathy Bhuvaragan [mailto:[email protected]] > Sent: Friday, July 22, 2016 2:43 PM > To: [email protected] > Cc: [email protected]; [email protected]; > [email protected]; Xue, Ying > Subject: [PATCH net-next v1 0/5] tipc: netlink updates for neighbour monitor > > This series contains the updates to configure and read the attributes for > neighbour monitor. > > Parthasarathy Bhuvaragan (5): > tipc: introduce constants for tipc address validation > tipc: make cluster size threshold for monitoring configurable > tipc: get monitor threshold for the cluster > tipc: add a function to get the bearer name > tipc: dump monitor attributes > > include/uapi/linux/tipc.h | 30 ++++++- > include/uapi/linux/tipc_netlink.h | 37 +++++++++ > net/tipc/addr.h | 5 +- > net/tipc/bearer.c | 25 +++++- > net/tipc/bearer.h | 1 + > net/tipc/monitor.c | 152 +++++++++++++++++++++++++++++++++++ > net/tipc/monitor.h | 9 +++ > net/tipc/netlink.c | 27 ++++++- > net/tipc/netlink.h | 1 + > net/tipc/node.c | 165 > ++++++++++++++++++++++++++++++++++++++ > net/tipc/node.h | 5 ++ > 11 files changed, 445 insertions(+), 12 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.http://sdm.link/zohodev2dev _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
