* receiver wakes up, it usually invokes msg_get() to pick
* the next message from the port.
*
+ * \note
+ * When you put a message into a port, such message becomes
+ * unavailable until you retrieve it using msg_get(), eg.
+ * you must not delete it or put it into another port.
+ *
* Message ports can hold any number of pending messages,
* and receivers usually process them in FIFO order.
* Other scheduling policies are possible, but not implemented
* } TestMsg;
*
*
- * static cpu_stack_t sender_stack[CONFIG_KERN_MINSTACKSIZE / sizeof(cpu_stack_t)];
+ * PROC_DEFINE_STACK(sender_stack, KERN_MINSTACKSIZE);
*
* // A process that sends two messages and waits for replies.
* static void sender_proc(void)
* }
* }
* \endcode
+ *
+ * $WIZ$ module_name = "msg"
+ * $WIZ$ module_depends = "event", "signal", "kernel"
*/