From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tony Breeds <tony@bakeyournoodle.com>
Subject: Re: Request for linux-next inclusion of the voyager tree
Date: Tue, 9 Jun 2009 09:28:53 +1000
Message-ID: <20090608232853.GG16602@bilbo.ozlabs.org>
References: <1244477423.4079.228.camel@mulgrave.site>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <linux-next-owner@vger.kernel.org>
Received: from bilbo.ozlabs.org ([203.10.76.25]:60649 "EHLO bilbo.ozlabs.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751404AbZFHX2v (ORCPT <rfc822;linux-next@vger.kernel.org>);
	Mon, 8 Jun 2009 19:28:51 -0400
Content-Disposition: inline
In-Reply-To: <1244477423.4079.228.camel@mulgrave.site>
Sender: linux-next-owner@vger.kernel.org
List-ID: <linux-next.vger.kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org

On Mon, Jun 08, 2009 at 11:10:23AM -0500, James Bottomley wrote:
> Could you add this (as a postmerge tree) somewhere after the x86 trees,
> please (it depends on the auto-x86-next branch).

I'm sure I've seen to somewhere before, but can you provide any relevant
details for building a voyager kernel (defconfig and crosscompile invocations
is probably all we need.)

Yours Tony