From: Blue Swirl <blauwirbel@gmail.com>
To: Alexandre Raymond <cerbere@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix compilation warning due to missing header for sigaction (followup)
Date: Sun, 5 Jun 2011 18:44:01 +0300 [thread overview]
Message-ID: <BANLkTimyRHr2DWkNqEZcLu9Hw1fGtbvNSw@mail.gmail.com> (raw)
In-Reply-To: <1307071609-1165-1-git-send-email-cerbere@gmail.com>
On Fri, Jun 3, 2011 at 6:26 AM, Alexandre Raymond <cerbere@gmail.com> wrote:
> This patch removes all references to signal.h when qemu-common.h is included
> as they become redundant.
This breaks the build. Maybe it depends on some previous patch? If so,
it would be nice to submit the patches as a series so that the patches
can be tested, now I could not find the other patch.
next prev parent reply other threads:[~2011-06-05 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 3:26 [Qemu-devel] [PATCH] Fix compilation warning due to missing header for sigaction (followup) Alexandre Raymond
2011-06-05 15:44 ` Blue Swirl [this message]
2011-06-05 16:49 ` Alexandre Raymond
2011-06-05 17:03 ` Blue Swirl
2011-06-07 13:53 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
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=BANLkTimyRHr2DWkNqEZcLu9Hw1fGtbvNSw@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=cerbere@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).