From 71c83bd0e0f8fa907f8fc91b3e5d9f98ad6a8466 Mon Sep 17 00:00:00 2001 From: Andre Puschmann Date: Fri, 22 Nov 2019 22:33:46 +0100 Subject: [PATCH] fixing typo in RRC proc --- srsue/src/stack/rrc/rrc_procedures.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/srsue/src/stack/rrc/rrc_procedures.cc b/srsue/src/stack/rrc/rrc_procedures.cc index f33f9faa2..c91e2625f 100644 --- a/srsue/src/stack/rrc/rrc_procedures.cc +++ b/srsue/src/stack/rrc/rrc_procedures.cc @@ -892,7 +892,7 @@ proc_outcome_t rrc::connection_reest_proc::init(asn1::rrc::reest_cause_e cause) // the initiation of reestablishment procedure as indicates in 3GPP 36.331 Section 5.3.7.2 // Cannot be called from here because it has PHY-MAC re-configuration that should be performed in a different thread - Info("Conditions are meet. Initiating RRC Connection Reestablishment Procedure\n"); + Info("Conditions are met. Initiating RRC Connection Reestablishment Procedure\n"); // stop timer T310, if running; rrc_ptr->t310.stop(); @@ -930,7 +930,7 @@ proc_outcome_t rrc::connection_reest_proc::init(asn1::rrc::reest_cause_e cause) // 3GPP 36.331 Section 5.3.7.1 // If AS security has not been activated, the UE does not initiate the procedure but instead // moves to RRC_IDLE directly - Info("Conditions are NOT meet\n"); + Info("Conditions are NOT met\n"); rrc_ptr->start_go_idle(); return proc_outcome_t::success; }