[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190319.135636.2009857992521742533.davem@davemloft.net>
Date: Tue, 19 Mar 2019 13:56:36 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: hoang.h.le@...tech.com.au
Cc: tipc-discussion@...ts.sourceforge.net, jon.maloy@...csson.com,
maloy@...jonn.com, ying.xue@...driver.com, netdev@...r.kernel.org
Subject: Re: [net-next v3 2/3] tipc: introduce new capability flag for
cluster
From: Hoang Le <hoang.h.le@...tech.com.au>
Date: Tue, 19 Mar 2019 18:49:49 +0700
> As a preparation for introducing a smooth switching between replicast
> and broadcast method for multicast message, We have to introduce a new
> capability flag TIPC_MCAST_RBCTL to handle this new feature.
>
> During a cluster upgrade a node can come back with this new capabilities
> which also must be reflected in the cluster capabilities field.
> The new feature is only applicable if all node in the cluster supports
> this new capability.
>
> Acked-by: Jon Maloy <jon.maloy@...csson.com>
> Signed-off-by: Hoang Le <hoang.h.le@...tech.com.au>
Applied.
Powered by blists - more mailing lists