From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.dvmed.net (srv5.dvmed.net [207.36.208.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id B112C67C40 for ; Fri, 9 Jun 2006 06:46:48 +1000 (EST) Message-ID: <44888CB3.1060507@garzik.org> Date: Thu, 08 Jun 2006 16:46:43 -0400 From: Jeff Garzik MIME-Version: 1.0 To: Jon Loeliger Subject: Re: [PATCH 9/10] Add Vitesse 8244 PHY for MPC8641 HPCN platform. References: <1149720298.23938.207.camel@cashmere.sps.mot.com> <44887BD3.7000009@garzik.org> <1149797603.23938.251.camel@cashmere.sps.mot.com> <44888A37.3090401@garzik.org> <1149799209.23938.256.camel@cashmere.sps.mot.com> In-Reply-To: <1149799209.23938.256.camel@cashmere.sps.mot.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: "linuxppc-dev@ozlabs.org" , Paul Mackerras , netdev@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Jon Loeliger wrote: > On Thu, 2006-06-08 at 15:36, Jeff Garzik wrote: >> Is it dependent on other stuff in Paul's tree? > > Yes, very much so. Most of this patch set is an > entirely new PPC board port against his arch/powerpc > basis. The new PHY is incidentally on that board, > but the patches for its introduction could be > introduced through the netdev tree if needed. > It would just need to be coordinated some. I am, > of course, willing to work it either way as needed. I leave it up to you and Paul to coordinate, then :) I'm fine with the patch, and if its better to merge via linuxppc.git, that's OK with me. If you would prefer to send it via my tree, to go ahead and get it in, that's fine too. Jeff From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH 9/10] Add Vitesse 8244 PHY for MPC8641 HPCN platform. Date: Thu, 08 Jun 2006 16:46:43 -0400 Message-ID: <44888CB3.1060507@garzik.org> References: <1149720298.23938.207.camel@cashmere.sps.mot.com> <44887BD3.7000009@garzik.org> <1149797603.23938.251.camel@cashmere.sps.mot.com> <44888A37.3090401@garzik.org> <1149799209.23938.256.camel@cashmere.sps.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "linuxppc-dev@ozlabs.org" , netdev@vger.kernel.org, Paul Mackerras Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:23257 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S964998AbWFHUqr (ORCPT ); Thu, 8 Jun 2006 16:46:47 -0400 To: Jon Loeliger In-Reply-To: <1149799209.23938.256.camel@cashmere.sps.mot.com> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Jon Loeliger wrote: > On Thu, 2006-06-08 at 15:36, Jeff Garzik wrote: >> Is it dependent on other stuff in Paul's tree? > > Yes, very much so. Most of this patch set is an > entirely new PPC board port against his arch/powerpc > basis. The new PHY is incidentally on that board, > but the patches for its introduction could be > introduced through the netdev tree if needed. > It would just need to be coordinated some. I am, > of course, willing to work it either way as needed. I leave it up to you and Paul to coordinate, then :) I'm fine with the patch, and if its better to merge via linuxppc.git, that's OK with me. If you would prefer to send it via my tree, to go ahead and get it in, that's fine too. Jeff