diff options
| author | Chris Johns <chrisj@rtems.org> | 2016-02-18 10:32:05 +1100 |
|---|---|---|
| committer | Amar Takhar <verm@darkbeer.org> | 2016-05-02 20:51:26 -0400 |
| commit | f02e87257aa62bd8b78fb199a33a3cf1a5ad18be (patch) | |
| tree | b8a1480e099194ebea5f67a22e488567468abb22 /c_user/semaphore_manager.rst | |
| parent | Manually apply patch from textinfo dooc. (diff) | |
| download | rtems-docs-f02e87257aa62bd8b78fb199a33a3cf1a5ad18be.tar.bz2 | |
Fix the double quotes.
Diffstat (limited to '')
| -rw-r--r-- | c_user/semaphore_manager.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/c_user/semaphore_manager.rst b/c_user/semaphore_manager.rst index 620dcbf..668c951 100644 --- a/c_user/semaphore_manager.rst +++ b/c_user/semaphore_manager.rst @@ -231,7 +231,7 @@ This example demonstrates the attribute_set parameter needed to create a local semaphore with the task priority waiting queue discipline. The attribute_set parameter passed to the ``rtems_semaphore_create`` directive could be either ``RTEMS_PRIORITY`` or ``RTEMS_LOCAL | RTEMS_PRIORITY``. The attribute_set -parameter can be set to``RTEMS_PRIORITY`` because ``RTEMS_LOCAL`` is the +parameter can be set to ``RTEMS_PRIORITY`` because ``RTEMS_LOCAL`` is the default for all created tasks. If a similar semaphore were to be known globally, then the attribute_set parameter would be ``RTEMS_GLOBAL | RTEMS_PRIORITY``. @@ -298,9 +298,9 @@ Obtaining Semaphore IDs When a semaphore is created, RTEMS generates a unique semaphore ID and assigns it to the created semaphore until it is deleted. The semaphore ID may be obtained by either of two methods. First, as the result of an invocation of -the``rtems_semaphore_create`` directive, the semaphore ID is stored in a user -provided location. Second, the semaphore ID may be obtained later using -the``rtems_semaphore_ident`` directive. The semaphore ID is used by other +the ``rtems_semaphore_create`` directive, the semaphore ID is stored in a user +provided location. Second, the semaphore ID may be obtained later using the +``rtems_semaphore_ident`` directive. The semaphore ID is used by other semaphore manager directives to access this semaphore. Acquiring a Semaphore @@ -341,7 +341,7 @@ Releasing a Semaphore --------------------- The ``rtems_semaphore_release`` directive is used to release the specified -semaphore. A simplified version of the``rtems_semaphore_release`` directive +semaphore. A simplified version of the ``rtems_semaphore_release`` directive can be described as follows: If there sre no tasks are waiting on this semaphore then increment the |