[PATCH 3/4] mmdevapi: Unlock buffer in case of ReleaseBuffer error.

[Joerg-Cyril.Hoehle at t-systems.com]

Hi,

this depends upon my previous patch. See bug 28056 for discussion.

I've turned WARN to ERR because I want to see possible failures
prior to deciding what error code (if any) to return in such a case.
In particular, we need thinking about the consequence of an error
for waveOutWrite and GetPosition.  More generally, how to return errors
from the asynchronous feeder thread into winmm?
How to make it not hang in case of errors (waiting for a particular
position to be reached that'll never happen because that much data
was not written)?

Regards,
	Jörg Höhle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-mmdevapi-Unlock-buffer-in-case-of-ReleaseBuffer-err.patch
Type: application/octet-stream
Size: 1796 bytes
Desc: 0002-mmdevapi-Unlock-buffer-in-case-of-ReleaseBuffer-err.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20110922/0dcad17a/attachment-0001.obj>