qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-stable <qemu-stable@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] block/curl: Implement the libcurl timer callback interface
Date: Thu, 16 Jan 2014 09:38:48 +0100	[thread overview]
Message-ID: <52D79A98.7050400@redhat.com> (raw)
In-Reply-To: <CAFEAcA_6T_rB5A1Z2wtK5YHPw1CSVeG+p2uQsxX5F-+4BFjBzg@mail.gmail.com>

Il 15/01/2014 23:15, Peter Maydell ha scritto:
> 
>> > +    curl_multi_socket_action(s->multi, CURL_SOCKET_TIMEOUT, 0, &running);
> The libcurl docs say "This function was added in libcurl 7.15.4, and
>  is deemed stable since 7.16.0. " So if we want to keep supporting
> pre-7.16 libcurl then we need to retain the multi_socket_all codepath.
> 
> On the other hand 7.16 was released in October 2006. What's
> the oldest version we actually care about?

I say 7.16 :)

Paolo

  reply	other threads:[~2014-01-16  8:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 17:23 [Qemu-devel] [PATCH] block/curl: Implement the libcurl timer callback interface Peter Maydell
2014-01-15 21:37 ` Richard W.M. Jones
2014-01-15 21:56   ` Peter Maydell
2014-01-16  8:40     ` Paolo Bonzini
2014-01-15 22:06 ` Paolo Bonzini
2014-01-15 22:15   ` Peter Maydell
2014-01-16  8:38     ` Paolo Bonzini [this message]
2014-01-16  9:55       ` Peter Maydell
2014-01-16 10:15         ` Paolo Bonzini
2014-01-16  9:12   ` Richard W.M. Jones
2014-01-16  9:24     ` Richard W.M. Jones
2014-01-16  9:52       ` Kevin Wolf
  -- strict thread matches above, loose matches on Subject: below --
2014-01-24 13:56 Paolo Bonzini
2014-01-24 15:01 ` 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=52D79A98.7050400@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).