From: Ewan Mellor Subject: Re: [XenPPC] Re: [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures Date: Tue, 3 Oct 2006 16:30:59 +0100 Message-ID: <20061003153059.GA8533@leeni.uk.xensource.com> References: <20061002122304.GC29149@leeni.uk.xensource.com> <1159888836.28737.15.camel@basalt.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1159888836.28737.15.camel@basalt.austin.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Hollis Blanchard Cc: Dan Smith , Xen-Devel , Tony Breeds , XenPPC-devel List-Id: xen-devel@lists.xenproject.org On Tue, Oct 03, 2006 at 10:20:36AM -0500, Hollis Blanchard wrote: > On Mon, 2006-10-02 at 13:23 +0100, Ewan Mellor wrote: > > On Mon, Oct 02, 2006 at 03:57:26PM +0800, Tony Breeds wrote: > > > > > Hi All, > > > These patches update the xm-test code to be more easily portable > > > to new architecture. This focus of this endeavor is PPC but I believe > > > that IA64 also benefits. > > > > > > Patch summary: > > > > > > 1: Instead of using a dated snapshot (which no longer exists) > > > use buildroot-snapshot. > > > > The last time I built a xm-test ramdisk, the buildroot-snapshot was broken, > > and I had to go back a few days to find a working one. I'm wary of using > > buildroot-snapshot for that reason. Does anyone work within the buildroot > > community? Perhaps we could persuade them to keep "released" versions around, > > rather than just the expiring, daily snapshots? > > Ewan, if you have some problem with patch 1/6, could you still apply the > rest to xen-unstable? 2/6 wouldn't apply cleanly, but should be easy to > do by hand. I've got no particular problem with these patches (we'll host the buildroot tar on xenbits, which was the only query). The tree's feature-frozen now though -- we're at RC2 -- so these will drop in immediately after the release. Ewan.