diff options
| author | Leo C | 2016-09-08 19:15:27 +0200 |
|---|---|---|
| committer | Leo C | 2016-09-08 19:15:27 +0200 |
| commit | 70702af1370e44e32fb2c3c507e4759a187b4fe5 (patch) | |
| tree | 5b75a408efadf5fccd8d5d481e91cce73a86897b /fatfs/doc/en/sync.html | |
| parent | 7b78a5a287827db9e9b16286f3604aef69b37c5c (diff) | |
| download | z180-stamp-70702af1370e44e32fb2c3c507e4759a187b4fe5.zip | |
Import fatfs R0.12bfatfs-0.12b
Diffstat (limited to 'fatfs/doc/en/sync.html')
| -rw-r--r-- | fatfs/doc/en/sync.html | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/fatfs/doc/en/sync.html b/fatfs/doc/en/sync.html index 3e86b7f..3c16ac4 100644 --- a/fatfs/doc/en/sync.html +++ b/fatfs/doc/en/sync.html @@ -36,7 +36,6 @@ FRESULT f_sync ( <a href="rc.html#ok">FR_OK</a>,
<a href="rc.html#de">FR_DISK_ERR</a>,
<a href="rc.html#ie">FR_INT_ERR</a>,
-<a href="rc.html#nr">FR_NOT_READY</a>,
<a href="rc.html#io">FR_INVALID_OBJECT</a>,
<a href="rc.html#tm">FR_TIMEOUT</a>
</p>
@@ -45,8 +44,8 @@ FRESULT f_sync ( <div class="para desc">
<h4>Description</h4>
-<p>The <tt>f_sync()</tt> function performs the same process as <tt>f_close()</tt> function but the file is left opened and can continue read/write/seek operations to the file. This is suitable for the applications that open files for a long time in write mode, such as data logger. Performing <tt>f_sync()</tt> function of periodic or immediataly after <tt>f_write()</tt> function can minimize the risk of data loss due to a sudden blackout or an unintentional media removal. For more information, refer to <a href="appnote.html#critical">application note</a>.</p>
-<p>However there is no sense in <tt>f_sync()</tt> function immediataly before <tt>f_close()</tt> function because it performs <tt>f_sync()</tt> function in it. In other words, the differnce between those functions is that the file object is invalidated or not.</p>
+<p>The <tt>f_sync</tt> function performs the same process as <tt>f_close</tt> function but the file is left opened and can continue read/write/seek operations to the file. This is suitable for the applications that open files for a long time in write mode, such as data logger. Performing <tt>f_sync</tt> function of periodic or immediataly after <tt>f_write</tt> function can minimize the risk of data loss due to a sudden blackout or an unintentional media removal. For more information, refer to <a href="appnote.html#critical">application note</a>.</p>
+<p>However there is no sense in <tt>f_sync</tt> function immediataly before <tt>f_close</tt> function because it performs <tt>f_sync</tt> function in it. In other words, the differnce between those functions is that the file object is invalidated or not.</p>
</div>
|