summaryrefslogtreecommitdiff
path: root/net/tipc/node.c
diff options
context:
space:
mode:
authorYing Xue <ying.xue@windriver.com>2012-11-16 09:51:29 +0400
committerPaul Gortmaker <paul.gortmaker@windriver.com>2012-11-22 16:50:50 +0400
commit818f4da526656a100c637b098be06316fd4624e4 (patch)
tree0b94923bf039d6f2972d9177bc713b3456511bae /net/tipc/node.c
parent3c294cb374bf7ad6f5c2763f994d75935fb7814d (diff)
downloadlinux-818f4da526656a100c637b098be06316fd4624e4.tar.xz
tipc: remove supportable flag from bclink structure
The "supportable" flag in bclink structure is a compatibility flag indicating whether a peer node is capable of receiving TIPC broadcast messages. However, all TIPC versions since tipc-1.5, and after the inclusion in the upstream Linux kernel in 2006, support this capability. It is highly unlikely that anybody is still using such an old version of TIPC, let alone that they want to mix it with TIPC-2.0 nodes. Therefore, we now remove the "supportable" flag. Signed-off-by: Ying Xue <ying.xue@windriver.com> Signed-off-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'net/tipc/node.c')
-rw-r--r--net/tipc/node.c8
1 files changed, 3 insertions, 5 deletions
diff --git a/net/tipc/node.c b/net/tipc/node.c
index d21db204e25a..6f3e9b35d27f 100644
--- a/net/tipc/node.c
+++ b/net/tipc/node.c
@@ -264,11 +264,9 @@ static void node_established_contact(struct tipc_node *n_ptr)
{
tipc_k_signal((Handler)tipc_named_node_up, n_ptr->addr);
- if (n_ptr->bclink.supportable) {
- n_ptr->bclink.acked = tipc_bclink_get_last_sent();
- tipc_bclink_add_node(n_ptr->addr);
- n_ptr->bclink.supported = 1;
- }
+ n_ptr->bclink.acked = tipc_bclink_get_last_sent();
+ tipc_bclink_add_node(n_ptr->addr);
+ n_ptr->bclink.supported = 1;
}
static void node_name_purge_complete(unsigned long node_addr)