From: George Dunlap <george.dunlap@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 2] xenoprof: Fix 32-on-64 bit (supplemental)
Date: Tue, 24 Jan 2012 16:17:27 +0000 [thread overview]
Message-ID: <1327421847.26455.362.camel@elijah> (raw)
In-Reply-To: <1327421609.26455.360.camel@elijah>
On Tue, 2012-01-24 at 16:13 +0000, George Dunlap wrote:
> Actually, please hold off on applying these for a minute -- I meant to
> cancel the send pending a final build check (both 32- and 64-bit), but
> it didn't work. I'll send an ACK when they're ready.
OK, I think things are all good.
ACKed-by: George Dunlap <george.dunlap@eu.citrix.com>
prev parent reply other threads:[~2012-01-24 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <patchbomb.1327421382@elijah>
2012-01-24 16:09 ` [PATCH 1 of 2] xenoprof: Use uint64_t explicitly for internal calls George Dunlap
2012-01-24 16:09 ` [PATCH 2 of 2] xenoprof: Make the escape code consistent across 32 and 64-bit xen George Dunlap
2012-01-24 16:13 ` [PATCH 0 of 2] xenoprof: Fix 32-on-64 bit (supplemental) George Dunlap
2012-01-24 16:17 ` George Dunlap [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=1327421847.26455.362.camel@elijah \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).