[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BN6PR15MB15532F160364995CC521E7C19AA20@BN6PR15MB1553.namprd15.prod.outlook.com>
Date: Thu, 29 Mar 2018 22:49:25 +0000
From: Jon Maloy <jon.maloy@...csson.com>
To: David Ahern <dsahern@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: Mohan Krishna Ghanta Krishnamurthy
<mohan.krishna.ghanta.krishnamurthy@...csson.com>,
Tung Quang Nguyen <tung.q.nguyen@...tech.com.au>,
Hoang Huu Le <hoang.h.le@...tech.com.au>,
Canh Duc Luu <canh.d.luu@...tech.com.au>,
"ying.xue@...driver.com" <ying.xue@...driver.com>,
"tipc-discussion@...ts.sourceforge.net"
<tipc-discussion@...ts.sourceforge.net>
Subject: RE: [iproute2-next 0/2] tipc: changes to addressing structure
> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-
> owner@...r.kernel.org] On Behalf Of David Ahern
> Sent: Thursday, March 29, 2018 13:59
> To: Jon Maloy <jon.maloy@...csson.com>; davem@...emloft.net;
> netdev@...r.kernel.org
> Cc: Mohan Krishna Ghanta Krishnamurthy
[..]
bit node addresses as an integer in hex format,
> >> i.e., we remove the assumption about an internal structure.
> >>
> >
> > Applied to iproute2-next. Thanks,
> >
>
> BTW, please consider adding json support to tipc. It will make tipc command
> more robust to changes in output format.
Yes, we will do that.
///jon
Powered by blists - more mailing lists