Karl Fessel
Karl Fessel
> ```c > /** > * @ingroup foo > * @{ > */ > > /** @} */ > ``` > creates a member group (between the braces) and places...
this has minor API changes
at least we wouldn't be alone with that https://github.com/zephyrproject-rtos/zephyr/blob/bba8641354bfbf83743c032c378a791b941ad7fc/include/zephyr/ipc/icmsg.h#L23-27
in the > hmm. I may be wrong > > > To avoid putting [\ingroup](https://www.doxygen.nl/manual/commands.html#cmdingroup) commands in the documentation for each member you can also group members together by the...
doxygen also reads some blocking/grouping from the comments and some from the source code
I think to understand the choice of command words and their why you would need to dig through the history of doxygen and maybe javadoc. Thanks for investigating
thank you for diving > A very simple approach to fixing this is replacing ingroup with addtogroup wherever ingroup addtogroup would need a group title i think -not sure it...
i tested with native tap on the other side of the connection i went for nc listening 12345 :heavy_check_mark: connecting with nc :heavy_check_mark: `nc fe80::xxxxxxxx:13e2%tapbr0 12345` close and reconnect with...
Since the behaviour (RIOT is either listening or sending) is intended i consider the tests successful. I think this example shows what it intends to show (how to do TCP...
@brummer-simon all tests are done with tap network setup: terminal 1 (T1): ``` $ nc -6 -l 23456 ``` terminal 2 (T2): ``` examples/sock_tcp_echo$ make all Building application "sock_tcp_echo" for...