From: "Richard W.M. Jones" <rjones@redhat.com>
To: 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
Subject: [PATCH v2] block/curl.c: Use explicit long constants in curl_easy_setopt calls
Date: Thu, 9 Oct 2025 15:08:30 +0100 [thread overview]
Message-ID: <20251009141026.4042021-1-rjones@redhat.com> (raw)
v1 was posted here:
https://patchwork.ozlabs.org/project/qemu-devel/patch/20251001124055.2743244-1-rjones@redhat.com/
In v2, I incorporated additional changes found by Chenxi Mao.
Rich.
next reply other threads:[~2025-10-09 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 14:08 Richard W.M. Jones [this message]
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 15:38 ` Richard Henderson
2025-10-10 3:39 ` Akihiko Odaki
2025-10-10 6:30 ` Thomas Huth
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=20251009141026.4042021-1-rjones@redhat.com \
--to=rjones@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=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).