From: "Zhang, Xiantao" <xiantao.zhang@intel.com>
To: Jes Sorensen <jes@sgi.com>, Avi Kivity <avi@qumranet.com>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: RE: [patch] ia64 - expose registers in struct kvm_regs
Date: Thu, 8 Jan 2009 21:50:26 +0800 [thread overview]
Message-ID: <706158FABBBA044BAD4FE898A02E4BC21C951F37@pdsmsx503.ccr.corp.intel.com> (raw)
In-Reply-To: <4965F888.5010906@sgi.com>
Avi can pickup it into kvm.git, and seems it is unnecessary to push into 2.6.29, right ?
Xiantao
Jes Sorensen wrote:
> Hi,
>
> I think this one got lost in the battle. Would you mind sticking it in
> or do you want me to send it to Tony?
>
> Cheers,
> Jes
WARNING: multiple messages have this Message-ID (diff)
From: "Zhang, Xiantao" <xiantao.zhang@intel.com>
To: kvm-ia64@vger.kernel.org
Subject: RE: [patch] ia64 - expose registers in struct kvm_regs
Date: Thu, 08 Jan 2009 13:50:26 +0000 [thread overview]
Message-ID: <706158FABBBA044BAD4FE898A02E4BC21C951F37@pdsmsx503.ccr.corp.intel.com> (raw)
In-Reply-To: <4965F888.5010906@sgi.com>
Avi can pickup it into kvm.git, and seems it is unnecessary to push into 2.6.29, right ?
Xiantao
Jes Sorensen wrote:
> Hi,
>
> I think this one got lost in the battle. Would you mind sticking it in
> or do you want me to send it to Tony?
>
> Cheers,
> Jes
next prev parent reply other threads:[~2009-01-08 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 12:58 [patch] ia64 - expose registers in struct kvm_regs Jes Sorensen
2009-01-08 12:58 ` Jes Sorensen
2009-01-08 13:50 ` Zhang, Xiantao [this message]
2009-01-08 13:50 ` Zhang, Xiantao
2009-01-08 14:12 ` Jes Sorensen
2009-01-08 14:12 ` Jes Sorensen
2009-01-08 14:01 ` Avi Kivity
2009-01-08 14:01 ` Avi Kivity
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=706158FABBBA044BAD4FE898A02E4BC21C951F37@pdsmsx503.ccr.corp.intel.com \
--to=xiantao.zhang@intel.com \
--cc=avi@qumranet.com \
--cc=jes@sgi.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.