[PATCH] osmo-bts[master]: cosmetic: fix some typos

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

Vadim Yanitskiy gerrit-no-reply at lists.osmocom.org
Sun Jun 4 11:28:08 UTC 2017


Review at  https://gerrit.osmocom.org/2840

cosmetic: fix some typos

Change-Id: Ib9172735bc7a05d9d7425a0e66dd90ff2569ee05
---
M include/osmo-bts/scheduler.h
M include/osmo-bts/scheduler_backend.h
M src/common/scheduler.c
M src/osmo-bts-trx/scheduler_trx.c
4 files changed, 8 insertions(+), 8 deletions(-)


  git pull ssh://gerrit.osmocom.org:29418/osmo-bts refs/changes/40/2840/1

diff --git a/include/osmo-bts/scheduler.h b/include/osmo-bts/scheduler.h
index 33a99bb..9dbc946 100644
--- a/include/osmo-bts/scheduler.h
+++ b/include/osmo-bts/scheduler.h
@@ -127,7 +127,7 @@
 	uint8_t			mf_period;	/* period of multiframe */
 	const struct trx_sched_frame *mf_frames; /* pointer to frame layout */
 
-	struct llist_head	dl_prims;	/* Queue primitves for TX */
+	struct llist_head	dl_prims;	/* Queue primitives for TX */
 
 	/* Channel states for all logical channels */
 	struct l1sched_chan_state chan_state[_TRX_CHAN_MAX];
@@ -160,7 +160,7 @@
 /*! \brief Handle a PH-TCH.req from L2 down to L1 */
 int trx_sched_tch_req(struct l1sched_trx *l1t, struct osmo_phsap_prim *l1sap);
 
-/*! \brief PHY informs us of new (current) GSM freme nunmber */
+/*! \brief PHY informs us of new (current) GSM frame number */
 int trx_sched_clock(struct gsm_bts *bts, uint32_t fn);
 
 /*! \brief handle an UL burst received by PHY */
diff --git a/include/osmo-bts/scheduler_backend.h b/include/osmo-bts/scheduler_backend.h
index e63b961..af1cfbf 100644
--- a/include/osmo-bts/scheduler_backend.h
+++ b/include/osmo-bts/scheduler_backend.h
@@ -29,7 +29,7 @@
 	trx_sched_dl_func	*dl_fn;
 	/*! \brief function to call when burst received from PHY */
 	trx_sched_ul_func	*ul_fn;
-	/*! \breif is this channel automatically active at start? */
+	/*! \brief is this channel automatically active at start? */
 	int			auto_active;
 };
 extern const struct trx_chan_desc trx_chan_desc[_TRX_CHAN_MAX];
diff --git a/src/common/scheduler.c b/src/common/scheduler.c
index 27b7630..121475a 100644
--- a/src/common/scheduler.c
+++ b/src/common/scheduler.c
@@ -105,7 +105,7 @@
 	  0,1,0,0,1,1,1,1,0,0,1,0,0,1,0,0,1,0,0,1,1,1,1,1,1,1, },
 };
 
-/*! \brief SCH trainign sequence (TS 05.02 Chapter 5.2.5) */
+/*! \brief SCH training sequence (TS 05.02 Chapter 5.2.5) */
 const ubit_t _sched_sch_train[64] = {
 	1,0,1,1,1,0,0,1,0,1,1,0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,1,1,1,1,
 	0,0,1,0,1,1,0,1,0,1,0,0,0,1,0,1,0,1,1,1,0,1,1,0,0,0,0,1,1,0,1,1,
@@ -584,7 +584,7 @@
 	enum trx_chan_type		dl_chan;
 	/*! \brief downlink block ID */
 	uint8_t				dl_bid;
-	/*! \breff uplink TRX channel type */
+	/*! \brief uplink TRX channel type */
 	enum trx_chan_type		ul_chan;
 	/*! \brief uplink block ID */
 	uint8_t				ul_bid;
@@ -1307,7 +1307,7 @@
 	uint8_t				period;
 	/*! \brief pointer to scheduling structure */
 	const struct trx_sched_frame	*frames;
-	/*! \brife human-readable name */
+	/*! \brief human-readable name */
 	const char 			*name;
 };
 
diff --git a/src/osmo-bts-trx/scheduler_trx.c b/src/osmo-bts-trx/scheduler_trx.c
index 9ec9592..8531d5c 100644
--- a/src/osmo-bts-trx/scheduler_trx.c
+++ b/src/osmo-bts-trx/scheduler_trx.c
@@ -570,7 +570,7 @@
 		}
 		if (msgb_l2len(msg_tch) != len) {
 			LOGP(DL1C, LOGL_ERROR, "Cannot send payload with "
-				"invalid length! (expecing %d, received %d)\n",
+				"invalid length! (expecting %d, received %d)\n",
 				len, msgb_l2len(msg_tch));
 free_bad_msg:
 			/* free message */
@@ -1354,7 +1354,7 @@
 	/* TCH or BFI */
 	/* Note on FN 19 or 20: If we received the last burst of a frame,
 	 * it actually starts at FN 8 or 9. A burst starting there, overlaps
-	 * with the slot 12, so an extra FN must be substracted to get correct
+	 * with the slot 12, so an extra FN must be subtracted to get correct
 	 * start of frame.
 	 */
 	return _sched_compose_tch_ind(l1t, tn,

-- 
To view, visit https://gerrit.osmocom.org/2840
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: newchange
Gerrit-Change-Id: Ib9172735bc7a05d9d7425a0e66dd90ff2569ee05
Gerrit-PatchSet: 1
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Owner: Vadim Yanitskiy <axilirator at gmail.com>



More information about the gerrit-log mailing list