From: Jeff Cody <jcody@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] block/nfs: fix build breakage due to missing includes
Date: Wed, 30 Mar 2016 10:03:44 -0400 [thread overview]
Message-ID: <20160330140344.GA17302@localhost.localdomain> (raw)
In-Reply-To: <1459341994-20567-1-git-send-email-stefanha@redhat.com>
On Wed, Mar 30, 2016 at 01:46:32PM +0100, Stefan Hajnoczi wrote:
> Header files included by almost every source files have been slimmed down
> recently to speed up the build and eliminate unnecessary dependencies. The
> block/nfs.c file must have been forgotten when build testing because it
> currently fails to build.
>
> This series adds the necessary #include statements to make block/nfs.c build
> successfully again.
>
> Stefan Hajnoczi (2):
> block/nfs: add missing #include "qapi/error.h"
> block/nfs: add missing #include "qemu/cutils.h"
>
> block/nfs.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> --
> 2.5.5
>
Thanks,
Applied to my block branch:
git://github.com/codyprime/qemu-kvm-jtc.git block
-Jeff
next prev parent reply other threads:[~2016-03-30 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 12:46 [Qemu-devel] [PATCH 0/2] block/nfs: fix build breakage due to missing includes Stefan Hajnoczi
2016-03-30 12:46 ` [Qemu-devel] [PATCH 1/2] block/nfs: add missing #include "qapi/error.h" Stefan Hajnoczi
2016-03-30 12:46 ` [Qemu-devel] [PATCH 2/2] block/nfs: add missing #include "qemu/cutils.h" Stefan Hajnoczi
2016-03-30 14:03 ` Jeff Cody [this message]
2016-03-30 20:48 ` [Qemu-devel] [PATCH 0/2] block/nfs: fix build breakage due to missing includes Stefan Weil
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=20160330140344.GA17302@localhost.localdomain \
--to=jcody@redhat.com \
--cc=pl@kamp.de \
--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 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).