[PATCH 1/4] rpcrt4: Fix a comment and move a WARN to where it really
indicates a problem, rather than falsely triggering on normal conditions.
Robert Shearman
rob at codeweavers.com
Mon Nov 13 05:45:48 CST 2006
---
dlls/rpcrt4/rpc_transport.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
-------------- next part --------------
diff --git a/dlls/rpcrt4/rpc_transport.c b/dlls/rpcrt4/rpc_transport.c
index 8d54af6..9d84839 100644
--- a/dlls/rpcrt4/rpc_transport.c
+++ b/dlls/rpcrt4/rpc_transport.c
@@ -115,16 +115,16 @@ static RPC_STATUS rpcrt4_conn_listen_pip
if (ConnectNamedPipe(npc->pipe, &npc->ovl))
return RPC_S_OK;
- WARN("Couldn't ConnectNamedPipe (error was %d)\n", GetLastError());
if (GetLastError() == ERROR_PIPE_CONNECTED) {
SetEvent(npc->ovl.hEvent);
return RPC_S_OK;
}
if (GetLastError() == ERROR_IO_PENDING) {
- /* FIXME: looks like we need to GetOverlappedResult here? */
+ /* will be completed in rpcrt4_protseq_np_wait_for_new_connection */
return RPC_S_OK;
}
npc->listening = FALSE;
+ WARN("Couldn't ConnectNamedPipe (error was %d)\n", GetLastError());
return RPC_S_OUT_OF_RESOURCES;
}
More information about the wine-patches
mailing list