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

[Chris Johns]

On 12/04/12 5:55 PM, Sebastian Huber wrote:
> 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.
>

Looks fine.

Thanks
Chris