From b2ab1923278152f85d3c2186372a14caf383c632 Mon Sep 17 00:00:00 2001 From: Pau Espin Pedrol Date: Wed, 16 Oct 2019 16:41:26 +0200 Subject: cosmetic: ss7: Fix trailing whitespace Change-Id: Ifd947c51067842b83ea43ce25ba0d652baff259b --- src/xua_as_fsm.c | 2 +- src/xua_default_lm_fsm.c | 2 +- src/xua_rkm.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/xua_as_fsm.c b/src/xua_as_fsm.c index 5757d63..541e52c 100644 --- a/src/xua_as_fsm.c +++ b/src/xua_as_fsm.c @@ -1,6 +1,6 @@ /* SCCP M3UA / SUA AS osmo_fsm according to RFC3868 4.3.1 / RFC4666 4.3.2 */ /* (C) Copyright 2017 by Harald Welte - * + * * All Rights reserved. * * SPDX-License-Identifier: GPL-2.0+ diff --git a/src/xua_default_lm_fsm.c b/src/xua_default_lm_fsm.c index 11a97a2..880f89c 100644 --- a/src/xua_default_lm_fsm.c +++ b/src/xua_default_lm_fsm.c @@ -21,7 +21,7 @@ /* The idea of this default Layer Manager is as follows: * - we wait until a SCTP connection is established * - we issue the ASP-UP request and wait for the ASP being in UP state - * - we wait if we receive a M-NOTIFY indication about any AS in this ASP + * - we wait if we receive a M-NOTIFY indication about any AS in this ASP * - if that's not received, we use RKM to register a routing context * for our locally configured ASP and expect a positive registration * result as well as a NOTIFY indication about AS-ACTIVE afterwards. diff --git a/src/xua_rkm.c b/src/xua_rkm.c index 4b760ee..f1ac551 100644 --- a/src/xua_rkm.c +++ b/src/xua_rkm.c @@ -207,7 +207,7 @@ static int handle_rkey_reg(struct osmo_ss7_asp *asp, struct xua_msg *inner, * is a slightly non-standard interpretation of M3UA RKM * which requires the SG to not have a-priori-knowledge of * all AS/RK in situations where the ASP are trusted. - */ + */ /* check if there is already an AS for this routing key */ as = osmo_ss7_as_find_by_rctx(asp->inst, rctx); -- cgit v1.2.3