From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/2] Block patches
Date: Mon, 25 Mar 2013 06:15:27 -0600 [thread overview]
Message-ID: <51503FDF.6000007@redhat.com> (raw)
In-Reply-To: <1364209249-30630-1-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On 03/25/2013 05:00 AM, Stefan Hajnoczi wrote:
> This tiny pull request contains build fixes for a regression introduced in the
> last pull request.
>
> Kevin and I investigated to find out why these build failures were missed.
> Both my buildslave and Kevin's workstation did not have the rbd libraries
> installed so block/rbd.c was not built.
>
> The buildslave now has the missing libraries and will warn us if block/rbd.c
> breaks again. Kevin has also installed the package so his local builds
> exercise the code.
>
> The mingw build is already failing in buildbot due to an unrelated issue. The
> bdrv_file_open() prototype warning was not spotted amongst all the other
> warnings.
Series: Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-03-25 12:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 11:00 [Qemu-devel] [PULL 0/2] Block patches Stefan Hajnoczi
2013-03-25 11:00 ` [Qemu-devel] [PATCH 1/2] rbd: fix compile error Stefan Hajnoczi
2013-03-25 11:00 ` [Qemu-devel] [PATCH 2/2] block: Add options QDict to bdrv_file_open() prototypes (fix MinGW build) Stefan Hajnoczi
2013-03-25 11:54 ` [Qemu-devel] [PULL 0/2] Block patches Richard W.M. Jones
2013-03-25 12:15 ` Eric Blake [this message]
2015-03-12 19:10 Stefan Hajnoczi
2015-03-13 11:00 ` Peter Maydell
2015-08-14 14:41 Stefan Hajnoczi
2015-08-14 15:52 ` Peter Maydell
2015-09-02 16:01 Stefan Hajnoczi
2015-09-03 10:14 ` Peter Maydell
2016-03-17 11:08 Stefan Hajnoczi
2016-03-17 12:43 ` Peter Maydell
2016-09-13 5:42 Jeff Cody
2016-09-13 11:59 ` Peter Maydell
2017-02-28 4:37 Jeff Cody
2017-02-28 14:49 ` Peter Maydell
2017-06-14 21:55 Jeff Cody
2017-06-14 22:26 ` no-reply
2017-06-15 4:30 ` Jeff Cody
2017-06-15 7:28 ` Juan Quintela
2017-06-20 10:13 ` Peter Maydell
2017-06-28 12:20 Stefan Hajnoczi
2017-06-28 12:48 ` Stefan Hajnoczi
2017-06-30 14:10 Fam Zheng
2017-06-30 16:55 ` Peter Maydell
2017-07-17 15:40 Stefan Hajnoczi
2017-07-18 13:13 ` Peter Maydell
2017-07-18 4:17 Jeff Cody
2017-07-18 20:13 ` Peter Maydell
2018-01-22 12:40 Stefan Hajnoczi
2018-01-22 13:54 ` Stefan Hajnoczi
2018-02-01 4:06 Jeff Cody
2018-02-02 10:57 ` Peter Maydell
2018-06-05 14:19 Jeff Cody
2018-06-05 15:11 ` Peter Maydell
2018-06-27 14:48 Stefan Hajnoczi
2018-06-28 16:43 ` Peter Maydell
2018-07-01 14:58 ` no-reply
2018-07-02 6:19 ` Fam Zheng
2018-08-22 3:43 Jeff Cody
2018-08-23 18:02 ` Peter Maydell
2018-10-12 1:50 Fam Zheng
2018-10-12 11:39 ` Peter Maydell
2018-10-29 13:56 Stefan Hajnoczi
2018-10-29 18:23 ` Peter Maydell
2018-12-12 9:52 Stefan Hajnoczi
2018-12-13 13:05 ` Peter Maydell
2019-01-14 16:34 Stefan Hajnoczi
2019-01-15 18:07 ` Peter Maydell
2019-08-22 15:53 Stefan Hajnoczi
2019-08-27 9:00 ` Peter Maydell
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=51503FDF.6000007@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@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 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.