From: Thomas Huth <thuth@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, odaki@rsg.ci.i.u-tokyo.ac.jp,
viktor.prutyanov@phystech.edu, hreitz@redhat.com,
kwolf@redhat.com, maochenxi@bosc.ac.cn, berrange@redhat.com,
peter.maydell@linaro.org,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v2] block/curl.c: Use explicit long constants in curl_easy_setopt calls
Date: Fri, 10 Oct 2025 08:30:13 +0200 [thread overview]
Message-ID: <d17e5041-198e-4a5a-a5a4-6ea226c6ea81@redhat.com> (raw)
In-Reply-To: <20251009141026.4042021-2-rjones@redhat.com>
On 09/10/2025 16.08, Richard W.M. Jones wrote:
> curl_easy_setopt takes a variable argument that depends on what
> CURLOPT you are setting. Some require a long constant. Passing a
> plain int constant is potentially wrong on some platforms.
>
> With warnings enabled, multiple warnings like this were printed:
>
> ../block/curl.c: In function ‘curl_init_state’:
> ../block/curl.c:474:13: warning: call to ‘_curl_easy_setopt_err_long’ declared with attribute warning: curl_easy_setopt expects a long argument [-Wattribute-warning]
> 474 | curl_easy_setopt(state->curl, CURLOPT_AUTOREFERER, 1) ||
> | ^
>
> Signed-off-by: Richard W.M. Jones <rjones@redhat.com>
> Signed-off-by: Chenxi Mao <maochenxi@bosc.ac.cn>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> block/curl.c | 10 +++++-----
> contrib/elf2dmp/download.c | 4 ++--
> 2 files changed, 7 insertions(+), 7 deletions(-)
Thanks, this seems to fix the broken freebsd job in our gitlab CI!
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2025-10-10 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 14:08 [PATCH v2] block/curl.c: Use explicit long constants in curl_easy_setopt calls Richard W.M. Jones
2025-10-09 14:08 ` Richard W.M. Jones
2025-10-09 15:38 ` Richard Henderson
2025-10-10 3:39 ` Akihiko Odaki
2025-10-10 6:30 ` Thomas Huth [this message]
2025-10-10 19:03 ` Richard Henderson
2025-10-13 12:16 ` Kevin Wolf
2025-10-13 12:23 ` Kevin Wolf
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=d17e5041-198e-4a5a-a5a4-6ea226c6ea81@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=maochenxi@bosc.ac.cn \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rjones@redhat.com \
--cc=viktor.prutyanov@phystech.edu \
/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).