All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Anton Johansson <anjo@rev.ng>,
	ale@rev.ng, hreitz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] block: Handle curl 7.55.0, 7.85.0 version changes
Date: Mon, 20 Feb 2023 15:09:11 +0000	[thread overview]
Message-ID: <877cwctlu6.fsf@linaro.org> (raw)
In-Reply-To: <Y+pKBVkzivH+Xwvb@redhat.com>


Kevin Wolf <kwolf@redhat.com> writes:

> Am 13.02.2023 um 14:28 hat Peter Maydell geschrieben:
>> On Mon, 23 Jan 2023 at 20:15, Anton Johansson via <qemu-devel@nongnu.org> wrote:
>> >
>> > * 7.55.0 deprecates CURLINFO_CONTENT_LENGTH_DOWNLOAD in favour of a *_T
>> >   version, which returns curl_off_t instead of a double.
>> > * 7.85.0 deprecates CURLOPT_PROTOCOLS and CURLOPT_REDIR_PROTOCOLS in
>> >   favour of *_STR variants, specifying the desired protocols via a
>> >   string.
>> >
>> > Signed-off-by: Anton Johansson <anjo@rev.ng>
>> 
>> Block folks -- this patch has been reviewed, are you going to
>> pick it up (with the Resolves: line added) ?
>
> Yes, I'm going through the patches right now that were stuck because the
> previous pull request was blocked by CI.
>
> Thanks, applied to the block branch.

I've also applied to my testing/next (for the same reason) just in case
the block branch doesn't go in soon.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      reply	other threads:[~2023-02-20 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 20:14 [PATCH] block: Handle curl 7.55.0, 7.85.0 version changes Anton Johansson via
2023-01-24  7:55 ` Philippe Mathieu-Daudé
2023-01-24  9:51 ` Peter Maydell
2023-02-13 13:28 ` Peter Maydell
2023-02-13 14:32   ` Kevin Wolf
2023-02-20 15:09     ` Alex Bennée [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=877cwctlu6.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=ale@rev.ng \
    --cc=anjo@rev.ng \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.