[PATCH 07/12] server: Introduce default async queue that's used if async is not explicitly queued in fd op.

[Jacek Caban]

Although (at least now) all read and write implementations always queue
async on success, it's not the case for ioctl. I think we should allow
simple ioctls without pending results to not care about explicitly
handling async objects, but those still need a queued async for proper
result reporting. We currently don't set events, queue APCs nor send
completion for them.

My initial thought was to make async object work better without
associated queue, but that leads to problems with references from an
async to fd.

Signed-off-by: Jacek Caban <jacek at codeweavers.com>
---
 server/async.c |  8 +++++++-
 server/fd.c    | 20 +++++++++++++++-----
 server/file.h  |  2 +-
 3 files changed, 23 insertions(+), 7 deletions(-)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0007-server-Introduce-default-async-queue-that-s-used-if-a.diff
Type: text/x-patch
Size: 5241 bytes
Desc: not available
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20170613/7108b891/attachment.bin>