[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191121.150304.1123396062175478961.davem@davemloft.net>
Date: Thu, 21 Nov 2019 15:03:04 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: hoang.h.le@...tech.com.au
Cc: jon.maloy@...csson.com, maloy@...jonn.com,
tipc-discussion@...ts.sourceforge.net, ying.xue@...driver.com,
netdev@...r.kernel.org
Subject: Re: [net-next] tipc: update replicast capability for broadcast
send link
From: Hoang Le <hoang.h.le@...tech.com.au>
Date: Thu, 21 Nov 2019 10:01:09 +0700
> When setting up a cluster with non-replicast/replicast capability
> supported. This capability will be disabled for broadcast send link
> in order to be backwards compatible.
>
> However, when these non-support nodes left and be removed out the cluster.
> We don't update this capability on broadcast send link. Then, some of
> features that based on this capability will also disabling as unexpected.
>
> In this commit, we make sure the broadcast send link capabilities will
> be re-calculated as soon as a node removed/rejoined a cluster.
>
> Acked-by: Jon Maloy <jon.maloy@...csson.com>
> Signed-off-by: Hoang Le <hoang.h.le@...tech.com.au>
Applied, thank you.
Powered by blists - more mailing lists