|author||Neels Hofmeyr <email@example.com>||2017-06-20 04:35:06 +0200|
|committer||Neels Hofmeyr <firstname.lastname@example.org>||2017-06-23 00:18:23 +0000|
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
Diffstat (limited to 'include/osmocom/core/bits.h')
1 files changed, 9 insertions, 9 deletions
diff --git a/include/osmocom/core/bits.h b/include/osmocom/core/bits.h
index 61af716c..17fe1c6a 100644
@@ -1,3 +1,11 @@
+/*! \file bits.h
+ * Osmocom bit level support code.
+ * NOTE on the endianess of pbit_t:
+ * Bits in a pbit_t are ordered MSB first, i.e. 0x80 is the first bit.
+ * Bit i in a pbit_t array is array[i/8] & (1<<(7-i%8))
@@ -9,15 +17,7 @@
/*! \defgroup bits soft, unpacked and packed bits
-/*! \file bits.h
- * Osmocom bit level support code
- * NOTE on the endianess of pbit_t:
- * Bits in a pbit_t are ordered MSB first, i.e. 0x80 is the first bit.
- * Bit i in a pbit_t array is array[i/8] & (1<<(7-i%8))
+ * \file bits.h */
typedef int8_t sbit_t; /*!< soft bit (-127...127) */
typedef uint8_t ubit_t; /*!< unpacked bit (0 or 1) */