104714394f
As the already existing macro K_MEM_SLAB_DEFINE results in two variable definitions, the preceding static modifier leads to a seemingly working solution, though linkage conflicts will occur when the same memory slab name is used across multiple modules. The new K_MEM_SLAB_DEFINE_STATIC macro duplicates the functionality of K_MEM_SLAB_DEFINE with the difference that the static keywords are internally prepended before both variable definitions. The implementation has been tested on my Zephyr project (the build issue faded out). The documentation has been updated altogether with all incorrect occurences of static K_MEM_SLAB_DEFINE. Signed-off-by: Pavel Hübner <pavel.hubner@hardwario.com> |
||
|---|---|---|
| .. | ||
| data_passing | ||
| memory | ||
| other | ||
| scheduling | ||
| smp | ||
| synchronization | ||
| threads | ||
| timing | ||
| index.rst | ||