From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound-mail-21.bluehost.com (outbound-mail-21.bluehost.com [70.103.189.16]) by ozlabs.org (Postfix) with SMTP id 96DDF689C4 for ; Wed, 18 Jan 2006 07:37:28 +1100 (EST) Message-ID: <43CD557C.6050308@secretlab.ca> Date: Tue, 17 Jan 2006 13:37:16 -0700 From: Grant Likely MIME-Version: 1.0 To: T Ziomek Subject: Re: [PATCH 00/10] Updated ML300 & ML403 patches References: <43CD5144.1070401@secretlab.ca> In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Cc: T Ziomek , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , T Ziomek wrote: > On Tue, 17 Jan 2006, Grant Likely wrote: >> T Ziomek wrote: >>> Grant Likely wrote: >>>> John Bonesio wrote: >>>>> Grant Likely wrote: >>>>> I'm replying to this email thread because Grant suggested there be >>>>> a GIT >>>>> tree for Virtex specific changes. <--- snip ---> >> >> mainline linux-2.6 tree has ml300 support >> >> ml300 platform bus support is pending for the powerpc.git tree >> ml403 support is pending for the powerpc.git tree >> >> powerpc.git is periodically pulled into linux-2.6 >> >> both are on kernel.org > > Meh, okay. But then what are the "Virtex specific changes" that would need > to be in Paul's linuxppc tree or anywhere but kernel.org? Basically, I was thinking about a 'development sandbox' that feeds into linux-2.6.git. However, if we can use Paul's powerpc tree, then I don't need to create yet-another-git-tree g. -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. (403) 663-0761