From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH] HSO: add option hso driver Date: Tue, 13 May 2008 19:26:48 -0400 Message-ID: <482A23B8.7050705@pobox.com> References: <20080513215134.GC6139@kroah.com> <20080513232727.21c74bb2@core> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Greg KH , netdev@vger.kernel.org, Andrew Bird , Javier Marcet , Filip Aben , Paulius Zaleckas , Oliver Neukum , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org To: Alan Cox Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:49223 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756654AbYEMX0z (ORCPT ); Tue, 13 May 2008 19:26:55 -0400 In-Reply-To: <20080513232727.21c74bb2@core> Sender: netdev-owner@vger.kernel.org List-ID: Alan Cox wrote: >> Jeff, please queue this up for 2.6.27 if there are no problems that you >> can see. It has been in the linux-next tree for a while, and many users >> are reporting that it is working for them. >> >> Or if you feel it's ok for 2.6.26, I will not object to that either :) > > Can we get it into 2.6.26 - its a driver for new hardware and the driver > is going to get a clean up for 2.6.27 anyway. > > Comments below are minor and I don't think blockers > > So for the serial side > > Acked-by: Alan Cox AFAIK new drivers are OK post-rc1, since no possibility of regression and it enables new users. However, an exception to that might be a super-huge driver slipped in at the last minute with no review (clearly not the case here) Jeff