netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Jon Maloy <jon.maloy@ericsson.com>,
	davem@davemloft.net, netdev@vger.kernel.org
Cc: mohan.krishna.ghanta.krishnamurthy@ericsson.com,
	tung.q.nguyen@dektech.com.au, hoang.h.le@dektech.com.au,
	canh.d.luu@dektech.com.au, ying.xue@windriver.com,
	tipc-discussion@lists.sourceforge.net
Subject: Re: [iproute2-next 0/2] tipc: changes to addressing structure
Date: Thu, 29 Mar 2018 11:52:09 -0600	[thread overview]
Message-ID: <01b6fe63-def9-4c67-cdb3-a88a07964f83@gmail.com> (raw)
In-Reply-To: <1522255934-497-1-git-send-email-jon.maloy@ericsson.com>

On 3/28/18 10:52 AM, Jon Maloy wrote:
> 1: We introduce ability to set/get 128-bit node identities
> 2: We rename 'net id' to 'cluster id' in the command API, 
>    of course in a compatible way.
> 3: We print out all 32-bit node addresses as an integer in hex format,
>    i.e., we remove the assumption about an internal structure.
> 

Applied to iproute2-next. Thanks,

  parent reply	other threads:[~2018-03-29 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 16:52 [iproute2-next 0/2] tipc: changes to addressing structure Jon Maloy
2018-03-28 16:52 ` [iproute2-next 1/2] tipc: introduce command for handling a new 128-bit node identity Jon Maloy
2018-03-28 16:52 ` [iproute2-next 2/2] tipc: change node address printout formats Jon Maloy
2018-03-29 17:52 ` David Ahern [this message]
2018-03-29 17:58   ` [iproute2-next 0/2] tipc: changes to addressing structure David Ahern
2018-03-29 22:49     ` Jon Maloy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01b6fe63-def9-4c67-cdb3-a88a07964f83@gmail.com \
    --to=dsahern@gmail.com \
    --cc=canh.d.luu@dektech.com.au \
    --cc=davem@davemloft.net \
    --cc=hoang.h.le@dektech.com.au \
    --cc=jon.maloy@ericsson.com \
    --cc=mohan.krishna.ghanta.krishnamurthy@ericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.q.nguyen@dektech.com.au \
    --cc=ying.xue@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).