libosmocore/include/osmocom/gsm/gsm0341.h

/*! \file gsm0341.h */

#pragma once

#include <osmocom/gsm/protocol/gsm_03_41.h>

struct gsm341_ms_message *
gsm0341_build_msg(void *ctx, uint8_t geo_scope, uint8_t msg_code,
		  uint8_t update, uint16_t msg_id, uint8_t dcs,
		  uint8_t page_total, uint8_t page_cur,
		  uint8_t *data, uint8_t len);
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 gsm0341.h /`

add missing gsm0341.h 2014-12-30 00:22:26 +00:00			`#pragma once`

			`#include <osmocom/gsm/protocol/gsm_03_41.h>`

			`struct gsm341_ms_message *`
			`gsm0341_build_msg(void *ctx, uint8_t geo_scope, uint8_t msg_code,`
			`uint8_t update, uint16_t msg_id, uint8_t dcs,`
			`uint8_t page_total, uint8_t page_cur,`
			`uint8_t *data, uint8_t len);`