From: Gregory Haskins <ghaskins@novell.com>
To: avi@redhat.com
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
sfr@canb.auug.org.au, kvm@vger.kernel.org
Subject: Re: [PATCH v2--refid=<20090521172122.bb12027c.sfr@canb.auug.org.au>] kvm: fix irqfd build failure discovered in linux-next
Date: Thu, 21 May 2009 09:31:01 -0400 [thread overview]
Message-ID: <4A155795.1080808@novell.com> (raw)
In-Reply-To: <20090521132723.8177.20321.stgit@dev.haskins.net>
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
Gregory Haskins wrote:
> Stephen Rothwell noted a build failure in arch != x86 in last nights
> linux-next tree, as noted here:
>
Typo on "stg-mail" command line caused the messed up subject above. Pls
ignore this mail in favor of the real v2 resend that followed this.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
prev parent reply other threads:[~2009-05-21 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 13:27 [PATCH v2--refid=<20090521172122.bb12027c.sfr@canb.auug.org.au>] kvm: fix irqfd build failure discovered in linux-next Gregory Haskins
2009-05-21 13:31 ` Gregory Haskins [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=4A155795.1080808@novell.com \
--to=ghaskins@novell.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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