From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Алексей Павлов" <alexey.pawlow@gmail.com>,
"Метлицкий Юрий Викторович" <winaes@narod.ru>,
"Biswapriyo Nath" <nathbappai@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 0/2] buildsys: Fix building with SASL on Windows
Date: Wed, 11 Mar 2020 19:38:33 +0100 [thread overview]
Message-ID: <03e337bb-4533-09de-2ed0-fc0ac83bdf3c@redhat.com> (raw)
In-Reply-To: <20200309122454.22551-1-philmd@redhat.com>
On 09/03/20 13:24, Philippe Mathieu-Daudé wrote:
> Fix a bug reported by Youry few months ago:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg625606.html
>
> Since v1:
> - addressed Daniel review (always define STRUCT_IOVEC_DEFINED)
>
> The Fedora docker image already uses the libsasl since commit
> 8ea5962f286. Add the similar package to the Debian (host) image.
>
> Philippe Mathieu-Daudé (2):
> configure: Fix building with SASL on Windows
> tests/docker: Install SASL library to extend code coverage on amd64
>
> configure | 4 +++-
> tests/docker/dockerfiles/debian-amd64.docker | 1 +
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-03-11 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 12:24 [PATCH v2 0/2] buildsys: Fix building with SASL on Windows Philippe Mathieu-Daudé
2020-03-09 12:24 ` [PATCH v2 1/2] configure: " Philippe Mathieu-Daudé
2020-03-09 12:30 ` Daniel P. Berrangé
2020-03-09 12:43 ` Philippe Mathieu-Daudé
2020-03-09 12:24 ` [PATCH v2 2/2] tests/docker: Install SASL library to extend code coverage on amd64 Philippe Mathieu-Daudé
2020-03-11 18:38 ` Paolo Bonzini [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=03e337bb-4533-09de-2ed0-fc0ac83bdf3c@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alexey.pawlow@gmail.com \
--cc=berrange@redhat.com \
--cc=fam@euphon.net \
--cc=nathbappai@gmail.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=winaes@narod.ru \
/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).