diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2021-04-27 19:54:12 +0200 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2021-04-28 09:03:49 +0200 |
commit | bc66c959004b0eb651f5028401eddaad46ae3e08 (patch) | |
tree | b29fb81b19b686e4bf159d90fe46dafc5937744f | |
parent | c-user: Clarify constraints (diff) | |
download | rtems-docs-bc66c959004b0eb651f5028401eddaad46ae3e08.tar.bz2 |
c-user: Fix typo "cod" -> "code"
-rw-r--r-- | c-user/message/directives.rst | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/c-user/message/directives.rst b/c-user/message/directives.rst index c154a3b..11ff105 100644 --- a/c-user/message/directives.rst +++ b/c-user/message/directives.rst @@ -864,12 +864,13 @@ this message queue. If the calling task chooses to return immediately and the queue is empty, then the directive returns immediately with the :c:macro:`RTEMS_UNSATISFIED` status -cod. If the calling task chooses to wait at the message queue and the queue is -empty, then the calling task is placed on the message wait queue and blocked. -If the queue was created with the :c:macro:`RTEMS_PRIORITY` option specified, -then the calling task is inserted into the wait queue according to its -priority. But, if the queue was created with the :c:macro:`RTEMS_FIFO` option -specified, then the calling task is placed at the rear of the wait queue. +code. If the calling task chooses to wait at the message queue and the queue +is empty, then the calling task is placed on the message wait queue and +blocked. If the queue was created with the :c:macro:`RTEMS_PRIORITY` option +specified, then the calling task is inserted into the wait queue according to +its priority. But, if the queue was created with the :c:macro:`RTEMS_FIFO` +option specified, then the calling task is placed at the rear of the wait +queue. .. rubric:: RETURN VALUES: |