[PATCH 3/4] libblock: Change error status to fatal error

[Sebastian Huber]

On 04/12/2012 09:40 AM, Chris Johns wrote:
> On 12/04/12 5:27 PM, Sebastian Huber wrote:
[...]
>> We already have special fatal errors for the different lock/unlock
>> operations:
>>
>> #define RTEMS_BLKDEV_FATAL_BDBUF_SYNC_LOCK RTEMS_BLKDEV_FATAL_ERROR(11)
>> #define RTEMS_BLKDEV_FATAL_BDBUF_SYNC_UNLOCK RTEMS_BLKDEV_FATAL_ERROR(12)
>> #define RTEMS_BLKDEV_FATAL_BDBUF_CACHE_LOCK RTEMS_BLKDEV_FATAL_ERROR(13)
>> #define RTEMS_BLKDEV_FATAL_BDBUF_CACHE_UNLOCK RTEMS_BLKDEV_FATAL_ERROR(14)
>>
>
> Can the status code in rtems_bdbuf_lock be tested for RTEMS_UNSATISFIED and
>
> #define RTEMS_BLKDEV_FATAL_BDBUF_NO_INIT RTEMS_BLKDEV_FATAL_ERROR(xx)
>
> be raised ?

I added now some documentation and comments, see attached patch.

The only possible error returned should be RTEMS_INVALID_ID since we use 
RTEMS_WAIT and RTEMS_NO_TIMEOUT.

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bdbuf.patch
Type: text/x-patch
Size: 6082 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120412/bdad2b47/attachment-0001.bin>