Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752491AbZGaQnz (ORCPT ); Fri, 31 Jul 2009 12:43:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752446AbZGaQny (ORCPT ); Fri, 31 Jul 2009 12:43:54 -0400 Received: from kroah.org ([198.145.64.141]:54123 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752440AbZGaQny (ORCPT ); Fri, 31 Jul 2009 12:43:54 -0400 Date: Fri, 31 Jul 2009 09:41:59 -0700 From: Greg KH To: Kay Sievers Cc: Alan Stern , Kernel development list Subject: Re: [PATCH] Driver core: add new device to bus's list before probing Message-ID: <20090731164159.GA25624@kroah.com> References: <20090731160544.GA3430@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1819 Lines: 43 On Fri, Jul 31, 2009 at 12:30:03PM -0400, Kay Sievers wrote: > On Fri, Jul 31, 2009 at 12:05, Greg KH wrote: > > On Thu, Jul 30, 2009 at 04:57:06PM -0400, Kay Sievers wrote: > >> On Thu, Jul 30, 2009 at 15:27, Alan Stern wrote: > > >> > Kay, do you want this merged into 2.6.31 or are you okay with waiting > >> > for 2.6.32-rc1? ?It changes a major core routine. ?On the other hand, > >> > the problem it fixes does affect real users. > >> > >> I think it should go into -next and we wait a few days. It seems like > >> the proper fix, but we should make sure, we didn't miss something. > >> > >> After that, it would be nice if we can get that into 2.6.31, as we > >> have several problems already, which are likely solved by this. > > > > But as this isn't a regression (it's how things always have worked, > > right?), > > Yeah, that sounds right, but I guess we have just been the needed bit > slower in the past, and with the recent speedups I would expect more > cases to uncover this issue. > > > I'm a bit leary of pushing it to .31 right now, so late in the > > release cycle. ?How about it goes to Linus for .32, and we backport it > > to -stable if it looks ok? > > Sure, sounds fine too. > > Would be good though to have it in -next soon. Three major distros are > preparing a new distro release at the moment, and they will likely > need to add that to their kernel to make this issue, USB firmware > loading, and similar things working again. It will show up in the next linux-next release. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/