qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] io: improve docs for QIOChannelSocket async functions
Date: Wed, 3 Feb 2016 14:43:48 +0000	[thread overview]
Message-ID: <20160203144348.GE12907@work-vm> (raw)
In-Reply-To: <1454507331-30729-1-git-send-email-berrange@redhat.com>

* Daniel P. Berrange (berrange@redhat.com) wrote:
> In the docs for qio_channel_socket_connect_async,
> qio_channel_socket_listen_async and
> qio_channel_socket_dgram_async, mention that the
> SocketAddress parameters are copied, so can be freed
> immediately.
> 
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

Thanks,

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>

> ---
>  include/io/channel-socket.h | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/include/io/channel-socket.h b/include/io/channel-socket.h
> index 810537e..70d06b4 100644
> --- a/include/io/channel-socket.h
> +++ b/include/io/channel-socket.h
> @@ -105,7 +105,9 @@ int qio_channel_socket_connect_sync(QIOChannelSocket *ioc,
>   * Attempt to connect to the address @addr. This method
>   * will run in the background so the caller will regain
>   * execution control immediately. The function @callback
> - * will be invoked on completion or failure.
> + * will be invoked on completion or failure. The @addr
> + * parameter will be copied, so may be freed as soon
> + * as this function returns without waiting for completion.
>   */
>  void qio_channel_socket_connect_async(QIOChannelSocket *ioc,
>                                        SocketAddress *addr,
> @@ -140,7 +142,9 @@ int qio_channel_socket_listen_sync(QIOChannelSocket *ioc,
>   * Attempt to listen to the address @addr. This method
>   * will run in the background so the caller will regain
>   * execution control immediately. The function @callback
> - * will be invoked on completion or failure.
> + * will be invoked on completion or failure. The @addr
> + * parameter will be copied, so may be freed as soon
> + * as this function returns without waiting for completion.
>   */
>  void qio_channel_socket_listen_async(QIOChannelSocket *ioc,
>                                       SocketAddress *addr,
> @@ -181,6 +185,9 @@ int qio_channel_socket_dgram_sync(QIOChannelSocket *ioc,
>   * This method will run in the background so the caller
>   * will regain execution control immediately. The function
>   * @callback will be invoked on completion or failure.
> + * The @localAddr and @remoteAddr parameters will be copied,
> + * so may be freed as soon as this function returns without
> + * waiting for completion.
>   */
>  void qio_channel_socket_dgram_async(QIOChannelSocket *ioc,
>                                      SocketAddress *localAddr,
> -- 
> 2.5.0
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

      reply	other threads:[~2016-02-03 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 13:48 [Qemu-devel] [PATCH] io: improve docs for QIOChannelSocket async functions Daniel P. Berrange
2016-02-03 14:43 ` Dr. David Alan Gilbert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160203144348.GE12907@work-vm \
    --to=dgilbert@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).