public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
To: "Zhang, Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Caleb Moore <cmoore-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org>
Subject: Re: IA64 KVM
Date: Thu, 08 Nov 2007 19:19:58 -0700	[thread overview]
Message-ID: <1194574798.4419.20.camel@bling> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC94EEFA-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>


On Fri, 2007-11-09 at 09:29 +0800, Zhang, Xiantao wrote:
> H, Alex/Akio 
>    Thanks for your suggestions. It is a surely good idea to create a
> IA64 mailing list to talk about the IA64-KVM.  But now we have to rebase
> them to latest commits before sending out, since the kvm source layout
> changed much recently.  Once the final source layout comes out, we will
> send out the source code soon.  I believe it should happen in very near
> future.   :-)

Hi Xiantao,

   Thanks for your work on KVM/ia64 and efforts to get it into the tree,
we definitely appreciate it.  If it's not too much work, I think many of
us would appreciate looking at any kind of snapshot of your tree, even
if it's out of date from what's currently upstream.  We're eager to
start understanding how it works ;)  Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-11-09  2:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  8:49 IA64 KVM Caleb Moore
     [not found] ` <1194511792.16060.8.camel-s4JzMB4ojaMt8xfdh1/dHeEGBmbFmoqDjBLMurt6cr7aRrIkyKz72Q@public.gmane.org>
2007-11-08 10:21   ` Zhang, Xiantao
     [not found]     ` <42DFA526FC41B1429CE7279EF83C6BDC94EE0B-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-08 16:00       ` Alex Williamson
2007-11-08 23:28         ` Akio Takebe
     [not found]           ` <2EC8225F08CEA1takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-09  1:29             ` Zhang, Xiantao
     [not found]               ` <42DFA526FC41B1429CE7279EF83C6BDC94EEFA-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-09  2:19                 ` Alex Williamson [this message]
2007-11-09 11:40                 ` Carsten Otte
2007-11-09  2:13         ` Caleb Moore
     [not found]           ` <1194574387.5321.53.camel-s4JzMB4ojaMt8xfdh1/dHeEGBmbFmoqDjBLMurt6cr7aRrIkyKz72Q@public.gmane.org>
2007-11-09  3:27             ` Dong, Eddie
     [not found]               ` <10EA09EFD8728347A513008B6B0DA77A02597332-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-12  8:09                 ` Isaku Yamahata
2007-11-09  8:09             ` Zhang, Xiantao

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=1194574798.4419.20.camel@bling \
    --to=alex.williamson-vxdhtt5mjny@public.gmane.org \
    --cc=cmoore-YbfuJp6tym7X/JP9YwkgDA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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