libosmocore/include/osmocom/gsm/bitvec_gsm.h

#pragma once

#include <osmocom/core/bitvec.h>
#include <osmocom/gsm/protocol/gsm_04_08.h>

/*! \defgroup bitvec helpers for GSM
 *  @{
 * \file bitvec_gsm.h */

void bitvec_add_range1024(struct bitvec *bv, const struct gsm48_range_1024 *r);

/*! @} */
Add function for appending range1024 to bitvec Add convenience function to append range1024 encoded data (see 3GPP TS 44.018 Annex J) to a given bitvec. 2016-04-22 17:28:09 +00:00			`#pragma once`

			`#include <osmocom/core/bitvec.h>`
			`#include <osmocom/gsm/protocol/gsm_04_08.h>`

			`/*! \defgroup bitvec helpers for GSM`
			`* @{`
doxygen: unify use of \file across the board Considering the various styles and implications found in the sources, edit scores of files to follow the same API doc guidelines around the doxygen grouping and the \file tag. Many files now show a short description in the generated API doc that was so far only available as C comment. The guidelines and reasoning behind it is documented at https://osmocom.org/projects/cellular-infrastructure/wiki/Guidelines_for_API_documentation In some instances, remove file comments and add to the corresponding group instead, to be shared among several files (e.g. bitvec). Change-Id: Ifa70e77e90462b5eb2b0457c70fd25275910c72b 2017-06-20 02:35:06 +00:00			`* \file bitvec_gsm.h */`
Add function for appending range1024 to bitvec Add convenience function to append range1024 encoded data (see 3GPP TS 44.018 Annex J) to a given bitvec. 2016-04-22 17:28:09 +00:00
			`void bitvec_add_range1024(struct bitvec bv, const struct gsm48_range_1024 r);`

			`/! @} /`