From xen-ia64-devel-bounces@lists.xen.org Fri Mar 23 06:53:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 06:53:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAyN6-0007KE-K5; Fri, 23 Mar 2012 06:53:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAyN4-0007Jv-R3 for xen-ia64-devel@lists.xen.org; Fri, 23 Mar 2012 06:53:11 +0000 Received: from [85.158.143.99:41416] by server-1.bemta-4.messagelabs.com id 0C/64-20925-5DD1C6F4; Fri, 23 Mar 2012 06:53:09 +0000 X-Env-Sender: kuwa@jp.fujitsu.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1332485586!14170223!1 X-Originating-IP: [192.51.44.35] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjUxLjQ0LjM1ID0+IDE0MDEx\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6709 invoked from network); 23 Mar 2012 06:53:08 -0000 Received: from fgwmail5.fujitsu.co.jp (HELO fgwmail5.fujitsu.co.jp) (192.51.44.35) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Mar 2012 06:53:08 -0000 Received: from m1.gw.fujitsu.co.jp (unknown [10.0.50.71]) by fgwmail5.fujitsu.co.jp (Postfix) with ESMTP id 8A7563EE0BC; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 7327C45DE54; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 4B01A45DE55; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 3D3771DB8052; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from flabmail.flab.fujitsu.co.jp (flabmail.flab.fujitsu.co.jp [10.25.192.37]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id F145A1DB804A; Fri, 23 Mar 2012 15:53:03 +0900 (JST) Received: from vskawa.flab.fujitsu.co.jp (vskawa.flab.fujitsu.co.jp [10.25.192.39]) by flabmail.flab.fujitsu.co.jp (8.14.4/8.14.4/110310-Fujitsu Labs. Domain Mail Master) with ESMTP id q2N6qw4t004268; Fri, 23 Mar 2012 15:53:03 +0900 (JST) X-AuditID: 0a19c027-b7b2eae000007ea7-fb-4f6c1dcf04d9 Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vskawa.flab.fujitsu.co.jp (Symantec Brightmail Gateway) with SMTP id EC.FC.32423.FCD1C6F4; Fri, 23 Mar 2012 15:53:03 +0900 (JST) Received: from eve.cad.flab.fujitsu.co.jp (eve.cad.flab.fujitsu.co.jp [10.25.228.68]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/110311-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id q2N6r36s003564; Fri, 23 Mar 2012 15:53:03 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by eve.cad.flab.fujitsu.co.jp (8.14.4/8.14.4) with ESMTP id q2N6r3J2004100; Fri, 23 Mar 2012 15:53:03 +0900 (JST) (envelope-from kuwa@jp.fujitsu.com) Date: Fri, 23 Mar 2012 15:52:49 +0900 (JST) Message-Id: <20120323.155249.425911897.kuwa@jp.fujitsu.com> To: JBeulich@suse.com From: "KUWAMURA Shin'ya" In-Reply-To: <4F69A3340200007800079D1B@nat28.tlf.novell.com> References: <4F69A3340200007800079D1B@nat28.tlf.novell.com> X-Mailer: Mew version 6.4.50 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 X-Brightmail-Tracker: AAAAAQAAAZE= Cc: xen-ia64-devel@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [Xen-ia64-devel] removal of ia64 port X-BeenThere: xen-ia64-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of the ia64 port of Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-ia64-devel-bounces@lists.xen.org Errors-To: xen-ia64-devel-bounces@lists.xen.org Hi Jan, Thank you for your work on ia64. I am sorry that ia64 remains broken for a long time. >>>>> On Wed, 21 Mar 2012 08:45:24 +0000 >>>>> JBeulich@suse.com("Jan Beulich") said: > > Given that the ia64 port hasn't really been maintained for the last couple > of years (I am apparently the only one to try to keep it building at least, > but I suspect that it has been non-functional for quite a while), I'd like to > propose to remove the port. After quite some time of trying to get an > opinion from Intel on this, I was now notified of their agreement to this > move. > From my pov, the only thing to discuss here is whether this should > happen right away, or after 4.2 went out (then with a formal removal > proposal in that release - the port's state isn't being reflected correctly > anyway in ./MAINTAINERS afaict). I hope that ia64 code remains in xen-unstable for the time being. I am inspecting the problem of hypervisor now. Current ia64 status is: - xen-4.0-testing: work It still work on ia64 with small fixes. I will send patches later. - xen-4.1-testing: probably work with xend - libxl does not work on ia64. - xen-unstable: not work - The hypervisor cannot boot. - It worked on ia64 in October, 2010. Best regards, -- KUWAMURA Shin'ya _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xen.org http://lists.xensource.com/xen-ia64-devel From xen-ia64-devel-bounces@lists.xen.org Fri Mar 23 06:53:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 06:53:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAyN6-0007KE-K5; Fri, 23 Mar 2012 06:53:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAyN4-0007Jv-R3 for xen-ia64-devel@lists.xen.org; Fri, 23 Mar 2012 06:53:11 +0000 Received: from [85.158.143.99:41416] by server-1.bemta-4.messagelabs.com id 0C/64-20925-5DD1C6F4; Fri, 23 Mar 2012 06:53:09 +0000 X-Env-Sender: kuwa@jp.fujitsu.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1332485586!14170223!1 X-Originating-IP: [192.51.44.35] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjUxLjQ0LjM1ID0+IDE0MDEx\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6709 invoked from network); 23 Mar 2012 06:53:08 -0000 Received: from fgwmail5.fujitsu.co.jp (HELO fgwmail5.fujitsu.co.jp) (192.51.44.35) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Mar 2012 06:53:08 -0000 Received: from m1.gw.fujitsu.co.jp (unknown [10.0.50.71]) by fgwmail5.fujitsu.co.jp (Postfix) with ESMTP id 8A7563EE0BC; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 7327C45DE54; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 4B01A45DE55; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 3D3771DB8052; Fri, 23 Mar 2012 15:53:04 +0900 (JST) Received: from flabmail.flab.fujitsu.co.jp (flabmail.flab.fujitsu.co.jp [10.25.192.37]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id F145A1DB804A; Fri, 23 Mar 2012 15:53:03 +0900 (JST) Received: from vskawa.flab.fujitsu.co.jp (vskawa.flab.fujitsu.co.jp [10.25.192.39]) by flabmail.flab.fujitsu.co.jp (8.14.4/8.14.4/110310-Fujitsu Labs. Domain Mail Master) with ESMTP id q2N6qw4t004268; Fri, 23 Mar 2012 15:53:03 +0900 (JST) X-AuditID: 0a19c027-b7b2eae000007ea7-fb-4f6c1dcf04d9 Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vskawa.flab.fujitsu.co.jp (Symantec Brightmail Gateway) with SMTP id EC.FC.32423.FCD1C6F4; Fri, 23 Mar 2012 15:53:03 +0900 (JST) Received: from eve.cad.flab.fujitsu.co.jp (eve.cad.flab.fujitsu.co.jp [10.25.228.68]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/110311-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id q2N6r36s003564; Fri, 23 Mar 2012 15:53:03 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by eve.cad.flab.fujitsu.co.jp (8.14.4/8.14.4) with ESMTP id q2N6r3J2004100; Fri, 23 Mar 2012 15:53:03 +0900 (JST) (envelope-from kuwa@jp.fujitsu.com) Date: Fri, 23 Mar 2012 15:52:49 +0900 (JST) Message-Id: <20120323.155249.425911897.kuwa@jp.fujitsu.com> To: JBeulich@suse.com From: "KUWAMURA Shin'ya" In-Reply-To: <4F69A3340200007800079D1B@nat28.tlf.novell.com> References: <4F69A3340200007800079D1B@nat28.tlf.novell.com> X-Mailer: Mew version 6.4.50 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 X-Brightmail-Tracker: AAAAAQAAAZE= Cc: xen-ia64-devel@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [Xen-ia64-devel] removal of ia64 port X-BeenThere: xen-ia64-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of the ia64 port of Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-ia64-devel-bounces@lists.xen.org Errors-To: xen-ia64-devel-bounces@lists.xen.org Hi Jan, Thank you for your work on ia64. I am sorry that ia64 remains broken for a long time. >>>>> On Wed, 21 Mar 2012 08:45:24 +0000 >>>>> JBeulich@suse.com("Jan Beulich") said: > > Given that the ia64 port hasn't really been maintained for the last couple > of years (I am apparently the only one to try to keep it building at least, > but I suspect that it has been non-functional for quite a while), I'd like to > propose to remove the port. After quite some time of trying to get an > opinion from Intel on this, I was now notified of their agreement to this > move. > From my pov, the only thing to discuss here is whether this should > happen right away, or after 4.2 went out (then with a formal removal > proposal in that release - the port's state isn't being reflected correctly > anyway in ./MAINTAINERS afaict). I hope that ia64 code remains in xen-unstable for the time being. I am inspecting the problem of hypervisor now. Current ia64 status is: - xen-4.0-testing: work It still work on ia64 with small fixes. I will send patches later. - xen-4.1-testing: probably work with xend - libxl does not work on ia64. - xen-unstable: not work - The hypervisor cannot boot. - It worked on ia64 in October, 2010. Best regards, -- KUWAMURA Shin'ya _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xen.org http://lists.xensource.com/xen-ia64-devel From xen-ia64-devel-bounces@lists.xen.org Fri Mar 30 08:55:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:55:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXcR-0001uI-Jr; Fri, 30 Mar 2012 08:55:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXcQ-0001u1-CH for xen-ia64-devel@lists.xen.org; Fri, 30 Mar 2012 08:55:38 +0000 Received: from [85.158.138.51:64988] by server-5.bemta-3.messagelabs.com id 7E/58-31925-805757F4; Fri, 30 Mar 2012 08:55:36 +0000 X-Env-Sender: kuwa@jp.fujitsu.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1333097733!18183655!1 X-Originating-IP: [192.51.44.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjUxLjQ0LjM2ID0+IDIwMDEz\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4129 invoked from network); 30 Mar 2012 08:55:36 -0000 Received: from fgwmail6.fujitsu.co.jp (HELO fgwmail6.fujitsu.co.jp) (192.51.44.36) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Mar 2012 08:55:36 -0000 Received: from m2.gw.fujitsu.co.jp (unknown [10.0.50.72]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 38B2B3EE0B5; Fri, 30 Mar 2012 17:55:31 +0900 (JST) Received: from smail (m2 [127.0.0.1]) by outgoing.m2.gw.fujitsu.co.jp (Postfix) with ESMTP id 1FEA845DE4D; Fri, 30 Mar 2012 17:55:31 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (s2.gw.fujitsu.co.jp [10.0.50.92]) by m2.gw.fujitsu.co.jp (Postfix) with ESMTP id 0614B45DD78; Fri, 30 Mar 2012 17:55:31 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id EE41FE08003; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from flabmail.flab.fujitsu.co.jp (flabmail.flab.fujitsu.co.jp [10.25.192.37]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id A93E9E08001; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from vskawa.flab.fujitsu.co.jp (vskawa.flab.fujitsu.co.jp [10.25.192.39]) by flabmail.flab.fujitsu.co.jp (8.14.4/8.14.4/110310-Fujitsu Labs. Domain Mail Master) with ESMTP id q2U8tClc002170; Fri, 30 Mar 2012 17:55:30 +0900 (JST) X-AuditID: 0a19c027-b7b67ae000002cc0-a5-4f757502d389 Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vskawa.flab.fujitsu.co.jp (Symantec Brightmail Gateway) with SMTP id 78.F5.11456.205757F4; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from eve.cad.flab.fujitsu.co.jp (eve.cad.flab.fujitsu.co.jp [10.25.228.68]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/110311-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id q2U8tUtW014604; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by eve.cad.flab.fujitsu.co.jp (8.14.4/8.14.4) with ESMTP id q2U8tUMX056076; Fri, 30 Mar 2012 17:55:30 +0900 (JST) (envelope-from kuwa@jp.fujitsu.com) Date: Fri, 30 Mar 2012 17:54:45 +0900 (JST) Message-Id: <20120330.175445.321377065.kuwa@jp.fujitsu.com> To: Ian.Campbell@citrix.com, JBeulich@suse.com From: "KUWAMURA Shin'ya" In-Reply-To: <1333012384.18810.45.camel@zakaz.uk.xensource.com> References: <20120323.155249.425911897.kuwa@jp.fujitsu.com> <4F6C49F7020000780007A763@nat28.tlf.novell.com> <1333012384.18810.45.camel@zakaz.uk.xensource.com> X-Mailer: xcite1.60> Mew version 6.5rc1 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 X-Brightmail-Tracker: AAAAAQAAAZE= Cc: xen-devel@lists.xen.org, xen-ia64-devel@lists.xen.org Subject: Re: [Xen-ia64-devel] [Xen-devel] removal of ia64 port X-BeenThere: xen-ia64-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of the ia64 port of Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-ia64-devel-bounces@lists.xen.org Errors-To: xen-ia64-devel-bounces@lists.xen.org Hi Ian and Jan, >>>>> On Thu, 29 Mar 2012 10:13:04 +0100 >>>>> Ian.Campbell@citrix.com(Ian Campbell) said: > > Kuwamura, what is your motivation for wanting to keeping the ia64 port > in 4.2 and beyond? As the result of my consideration, I agree that ia64 port will be dropped on xen-unstable, since it seems to be hardly needed: - There was little discussion on xen-ia64-devel ML recently. - There are few Xen ia64 developers. - No new feature will be added. Best regards, -- KUWAMURA Shin'ya _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xen.org http://lists.xensource.com/xen-ia64-devel From xen-ia64-devel-bounces@lists.xen.org Fri Mar 30 08:55:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:55:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXcR-0001uI-Jr; Fri, 30 Mar 2012 08:55:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXcQ-0001u1-CH for xen-ia64-devel@lists.xen.org; Fri, 30 Mar 2012 08:55:38 +0000 Received: from [85.158.138.51:64988] by server-5.bemta-3.messagelabs.com id 7E/58-31925-805757F4; Fri, 30 Mar 2012 08:55:36 +0000 X-Env-Sender: kuwa@jp.fujitsu.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1333097733!18183655!1 X-Originating-IP: [192.51.44.36] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjUxLjQ0LjM2ID0+IDIwMDEz\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4129 invoked from network); 30 Mar 2012 08:55:36 -0000 Received: from fgwmail6.fujitsu.co.jp (HELO fgwmail6.fujitsu.co.jp) (192.51.44.36) by server-15.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Mar 2012 08:55:36 -0000 Received: from m2.gw.fujitsu.co.jp (unknown [10.0.50.72]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 38B2B3EE0B5; Fri, 30 Mar 2012 17:55:31 +0900 (JST) Received: from smail (m2 [127.0.0.1]) by outgoing.m2.gw.fujitsu.co.jp (Postfix) with ESMTP id 1FEA845DE4D; Fri, 30 Mar 2012 17:55:31 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (s2.gw.fujitsu.co.jp [10.0.50.92]) by m2.gw.fujitsu.co.jp (Postfix) with ESMTP id 0614B45DD78; Fri, 30 Mar 2012 17:55:31 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id EE41FE08003; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from flabmail.flab.fujitsu.co.jp (flabmail.flab.fujitsu.co.jp [10.25.192.37]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id A93E9E08001; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from vskawa.flab.fujitsu.co.jp (vskawa.flab.fujitsu.co.jp [10.25.192.39]) by flabmail.flab.fujitsu.co.jp (8.14.4/8.14.4/110310-Fujitsu Labs. Domain Mail Master) with ESMTP id q2U8tClc002170; Fri, 30 Mar 2012 17:55:30 +0900 (JST) X-AuditID: 0a19c027-b7b67ae000002cc0-a5-4f757502d389 Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vskawa.flab.fujitsu.co.jp (Symantec Brightmail Gateway) with SMTP id 78.F5.11456.205757F4; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from eve.cad.flab.fujitsu.co.jp (eve.cad.flab.fujitsu.co.jp [10.25.228.68]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/110311-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id q2U8tUtW014604; Fri, 30 Mar 2012 17:55:30 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by eve.cad.flab.fujitsu.co.jp (8.14.4/8.14.4) with ESMTP id q2U8tUMX056076; Fri, 30 Mar 2012 17:55:30 +0900 (JST) (envelope-from kuwa@jp.fujitsu.com) Date: Fri, 30 Mar 2012 17:54:45 +0900 (JST) Message-Id: <20120330.175445.321377065.kuwa@jp.fujitsu.com> To: Ian.Campbell@citrix.com, JBeulich@suse.com From: "KUWAMURA Shin'ya" In-Reply-To: <1333012384.18810.45.camel@zakaz.uk.xensource.com> References: <20120323.155249.425911897.kuwa@jp.fujitsu.com> <4F6C49F7020000780007A763@nat28.tlf.novell.com> <1333012384.18810.45.camel@zakaz.uk.xensource.com> X-Mailer: xcite1.60> Mew version 6.5rc1 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 X-Brightmail-Tracker: AAAAAQAAAZE= Cc: xen-devel@lists.xen.org, xen-ia64-devel@lists.xen.org Subject: Re: [Xen-ia64-devel] [Xen-devel] removal of ia64 port X-BeenThere: xen-ia64-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of the ia64 port of Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-ia64-devel-bounces@lists.xen.org Errors-To: xen-ia64-devel-bounces@lists.xen.org Hi Ian and Jan, >>>>> On Thu, 29 Mar 2012 10:13:04 +0100 >>>>> Ian.Campbell@citrix.com(Ian Campbell) said: > > Kuwamura, what is your motivation for wanting to keeping the ia64 port > in 4.2 and beyond? As the result of my consideration, I agree that ia64 port will be dropped on xen-unstable, since it seems to be hardly needed: - There was little discussion on xen-ia64-devel ML recently. - There are few Xen ia64 developers. - No new feature will be added. Best regards, -- KUWAMURA Shin'ya _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xen.org http://lists.xensource.com/xen-ia64-devel