On Wed, Feb 28, 2018 at 09:20:47AM +, Daniel P. Berrangé wrote:
> On Wed, Feb 28, 2018 at 01:06:30PM +0800, Peter Xu wrote:
> > Let qio_channel_socket_connect_async() return the created QIOTask object
> > for the async connection. In tcp chardev, cache that in SocketChardev
> > for further use
On Wed, Feb 28, 2018 at 01:06:30PM +0800, Peter Xu wrote:
> Let qio_channel_socket_connect_async() return the created QIOTask object
> for the async connection. In tcp chardev, cache that in SocketChardev
> for further use. With the QIOTask refcount, this is pretty safe.
Why do you want to retur
Let qio_channel_socket_connect_async() return the created QIOTask object
for the async connection. In tcp chardev, cache that in SocketChardev
for further use. With the QIOTask refcount, this is pretty safe.
Since at it, generalize out tcp_chr_socket_connect_async() since the
logic is used in bo