From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] curl: Cast fd to int for DPRINTF
Date: Mon, 1 Aug 2016 12:41:37 -0400 [thread overview]
Message-ID: <abd48ab4-4fd2-9e5e-c680-cbac5396f594@redhat.com> (raw)
In-Reply-To: <1470027888-24381-1-git-send-email-famz@redhat.com>
On 08/01/2016 01:04 AM, Fam Zheng wrote:
> Currently "make docker-test-mingw@fedora" has a warning like:
>
> /tmp/qemu-test/src/block/curl.c: In function 'curl_sock_cb':
> /tmp/qemu-test/src/block/curl.c:172:6: warning: format '%d' expects
> argument of type 'int', but argument 4 has type 'curl_socket_t {aka long
> long unsigned int}'
> DPRINTF("CURL (AIO): Sock action %d on fd %d\n", action, fd);
> ^
> cc1: all warnings being treated as errors
>
> Cast to int to suppress it.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/curl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/curl.c b/block/curl.c
> index da9f5e8..426fb4d 100644
> --- a/block/curl.c
> +++ b/block/curl.c
> @@ -169,7 +169,7 @@ static int curl_sock_cb(CURL *curl, curl_socket_t fd, int action,
> state->sock_fd = fd;
> s = state->s;
>
> - DPRINTF("CURL (AIO): Sock action %d on fd %d\n", action, fd);
> + DPRINTF("CURL (AIO): Sock action %d on fd %d\n", action, (int)fd);
> switch (action) {
> case CURL_POLL_IN:
> aio_set_fd_handler(s->aio_context, fd, false,
>
Is curl_socket_t always of type long long unsigned int? why not use %llu ?
(...Yeah, I know, we're probably not going to be dealing with FDs above
2-4 billion, just curious...)
--js
Benefit of doubt (this cast is almost certain to never do the wrong
thing, and even if it did, it's just a dprintf)
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2016-08-01 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 5:04 [Qemu-devel] [PATCH] curl: Cast fd to int for DPRINTF Fam Zheng
2016-08-01 16:41 ` John Snow [this message]
2016-08-02 1:09 ` Fam Zheng
2016-08-02 2:59 ` John Snow
2016-08-10 2:41 ` Fam Zheng
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=abd48ab4-4fd2-9e5e-c680-cbac5396f594@redhat.com \
--to=jsnow@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).