From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep Date: Thu, 27 May 2004 15:32:29 -0400 Sender: prism54-devel-admin@prism54.org Message-ID: <40B6424D.7030203@pobox.com> References: <20040524083003.GA3330@ruslug.rutgers.edu> <20040524085727.GR3330@ruslug.rutgers.edu> <40B62F29.6090101@pobox.com> <20040527192733.GB14186@logos.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Andrew Morton , linux-kernel@vger.kernel.org, netdev@oss.sgi.com, prism54-devel@prism54.org Return-path: To: Marcelo Tosatti , "Luis R. Rodriguez" In-Reply-To: <20040527192733.GB14186@logos.cnet> Errors-To: prism54-devel-admin@prism54.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netdev.vger.kernel.org Marcelo Tosatti wrote: > IMO support for new hardware (new drivers) which dont break existing setups are fine. > > Jeff, you are actively maintaining most of the network drivers in v2.4, if you are OK with the > inclusion of this, I'm OK. > > Does this make sense? Yup, makes sense and sounds good to me. Luis, feel free to send me the 2.4.x version of the prism54 driver -- after addressing my comments, of course ;-) Jeff