[PATCH] rtems: Fix no protocol mutex release

[Chris Johns]

On 07/06/2016 17:31, Sebastian Huber wrote:
> Yes, its definitely worth to discuss this. My preferred solution would
> be to go away from the objects and treat the Classic objects as a legacy
> component.

I am not sure about the term legacy component but I see what you are 
saying. For new application user have a range of alternatives to choose 
from and these are not fully proven or in a release. I am not sure what 
sort of footprint they have as I have not seen any real data so are they 
suitable for small memory devices?

The Classic API has a wide user base and there is a lot of code using it 
and some has a long life cycle. I do not see the Classic API going away 
in the near, medium or long term. If there is a way to improve the 
existing Classic API via a separate mutex then we should consider it. I 
think this is a good idea. It is cleaner and less likely to cause the 
errors we are seeing.

Chris