| commit | 08b758b4820ca65791894a268f7bcd2964f66c31 | |
| author | Daniel P. Berrange <berrange@redhat.com> | |
| Wed, 9 Mar 2016 16:49:56 +0000 (9 16:49 +0000) | ||
| committer | Daniel P. Berrange <berrange@redhat.com> | |
| Thu, 10 Mar 2016 17:19:07 +0000 (10 17:19 +0000) | ||
| tree | 8d0c52987398c0706bccebfd14353f8bb65ec5c9 | treesnapshot (tar.gz zip) |
| parent | 317856cac87b2aa15d03982262a436f1d3d0a2b3 | commitdiff |
char: remove qemu_chr_open_socket_fd method
The qemu_chr_open_socket_fd method takes care of either doing a
synchronous socket connect, or creating a listener socket. Part
of the work when creating the listener socket is to register a
watch for incoming clients. The caller of qemu_chr_open_socket_fd
may not want this watch created, as it might be doing a synchronous
wait for the first client. Rather than passing yet more parameters
into qemu_chr_open_socket_fd to let it handle this, just remove
the qemu_chr_open_socket_fd method an inline its functionality
into the caller. This allows for a clearer control flow and shorter
code.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
The qemu_chr_open_socket_fd method takes care of either doing a
synchronous socket connect, or creating a listener socket. Part
of the work when creating the listener socket is to register a
watch for incoming clients. The caller of qemu_chr_open_socket_fd
may not want this watch created, as it might be doing a synchronous
wait for the first client. Rather than passing yet more parameters
into qemu_chr_open_socket_fd to let it handle this, just remove
the qemu_chr_open_socket_fd method an inline its functionality
into the caller. This allows for a clearer control flow and shorter
code.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
| qemu-char.c | diffblobblamehistory |