rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-07-25 07:13:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

filesystem: Fix numbered lists.

Browse Source
This commit is contained in:
Joel Sherrill 2016-10-28 15:56:47 -05:00
parent 01a36eedc5
commit 790fcab1d5
1 changed files with 39 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

62
filesystem/call_development.rst
View File

@ -13,57 +13,57 @@ standards if a specific interface has been established. The list below
represents the routines that have been included as part of the application's represents the routines that have been included as part of the application's
interface. interface.
# access() #. access()
# chdir() # .chdir()
# chmod() #. chmod()
# chown() #. chown()
# close() #. close()
# closedir() #. closedir()
# dup() #. dup()
# dup2() #. dup2()
# fchmod() #. fchmod()
# fcntl() #. fcntl()
# fdatasync() #. fdatasync()
# fpathconf() #. fpathconf()
# fstat() #. fstat()
# ioctl() #. ioctl()
# link() #. link()
# lseek() #. lseek()
# mkdir() #. mkdir()
# mkfifo() #. mkfifo()
# mknod() #. mknod()
# mount() #. mount()
# open() #. open()
# opendir() #. opendir()
# pathconf() #. pathconf()
# read() #. read()
# readdir() #. readdir()
# unmount() #. unmount()
The sections that follow provide developmental information concerning each of The sections that follow provide developmental information concerning each of
these functions. these functions.
@ -218,12 +218,12 @@ descriptor refers to an element of the RTEMS filesystem.
The following sequence will be performed for any filesystem file descriptor: The following sequence will be performed for any filesystem file descriptor:
# Use the ``rtems_libio_iop()`` function to obtain the ``rtems_libio_t`` #. Use the ``rtems_libio_iop()`` function to obtain the ``rtems_libio_t``
structure for the file descriptor structure for the file descriptor
# Range check the file descriptor using ``rtems_libio_check_fd()`` #. Range check the file descriptor using ``rtems_libio_check_fd()``
# Determine if there is actually a function in the selected handler table that #. Determine if there is actually a function in the selected handler table that
processes the ``close()`` operation for the filesystem and node type processes the ``close()`` operation for the filesystem and node type
selected. This is generally done to avoid execution attempts on functions selected. This is generally done to avoid execution attempts on functions
that have not been implemented. that have not been implemented.
@ -231,10 +231,10 @@ The following sequence will be performed for any filesystem file descriptor:
# If the function has been defined it is invoked with the file control # If the function has been defined it is invoked with the file control
block pointer as its argument. block pointer as its argument.
# The file control block that was associated with the open file descriptor is #. The file control block that was associated with the open file descriptor is
marked as free using ``rtems_libio_free()``. marked as free using ``rtems_libio_free()``.
# The return code from the close handler is then passed back to the calling #. The return code from the close handler is then passed back to the calling
program. program.
closedir closedir