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 20:03:40 +0300 [thread overview]
Message-ID: <BANLkTikJtOcUdPFMcOrT_1LcaYG3ryU2QQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=HKTVJQiroEN9v64gFgR4-J_rC9g@mail.gmail.com>
On Sun, Jun 5, 2011 at 7:49 PM, Alexandre Raymond <cerbere@gmail.com> wrote:
> Hi Blue,
>
> This patch indeed depends on http://patchwork.ozlabs.org/patch/98325/.
>
> Since it had already been applied by Andreas to the trivial tree, I
> didn't think it was necessary to resend it in the followup.
>
> If you prefer, I can resend both in the same series.
No need, I think this should also go via trivial patches queue. The
patch looks fine to me.
next prev parent reply other threads:[~2011-06-05 17:04 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
2011-06-05 16:49 ` Alexandre Raymond
2011-06-05 17:03 ` Blue Swirl [this message]
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=BANLkTikJtOcUdPFMcOrT_1LcaYG3ryU2QQ@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).