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
diff --git a/src/logging_gsmtap.c b/src/logging_gsmtap.c
index 9e5884b..d0aa47b 100644
--- a/src/logging_gsmtap.c
+++ b/src/logging_gsmtap.c
@@ -1,6 +1,12 @@
-/* GSMTAP network logging support code */
-
-/* (C) 2016 by Harald Welte <laforge@gnumonks.org>
+/*! \file logging_gsmtap.c
+ * libosmocore log output encapsulated in GSMTAP.
+ *
+ * Encapsulating the log output inside GSMTAP frames allows us to
+ * observer protocol traces (of Um, Abis, A or any other interface in
+ * the Osmocom world) with synchronous interspersed log messages.
+ */
+/*
+ * (C) 2016 by Harald Welte <laforge@gnumonks.org>
* All Rights Reserved
*
* This program is free software; you can redistribute it and/or modify
@@ -21,15 +27,7 @@
/*! \addtogroup logging
* @{
- */
-
-/*! \file logging_gsmtap.c
- * libosmocore log output encapsulated in GSMTAP
- *
- * Encapsulating the log output inside GSMTAP frames allows us to
- * observer protocol traces (of Um, Abis, A or any other interface in
- * the Osmocom world) with synchronous interspersed log messages.
- */
+ * \file logging_gsmtap.c */
#include "../config.h"