Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759447AbYARLdn (ORCPT ); Fri, 18 Jan 2008 06:33:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754200AbYARLdg (ORCPT ); Fri, 18 Jan 2008 06:33:36 -0500 Received: from fg-out-1718.google.com ([72.14.220.157]:18980 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754034AbYARLdf (ORCPT ); Fri, 18 Jan 2008 06:33:35 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=YQw90lZuKZkPeLFv1rgLoTVQg+wb6zRUDZTVg/m7HikahMGAvGKQZJeTkd003yiP6lFXF0hBHswtPCy8LFcSZFhY65PBEFx0/AYI62cFPP1Xs3/aZr3AxfHAdap9a8CmPY00QaoRQRD/R7bcajOEfOury5ptnvbzogbuZYRenho= Date: Fri, 18 Jan 2008 12:40:01 +0100 From: Jarek Poplawski To: Kay Sievers Cc: Dave Young , Alan Stern , Greg KH , stefanr@s5r6.in-berlin.de, David Brownell , Kernel development list Subject: Re: [PATCH 7/7] driver-core : convert semaphore to mutex in struct class Message-ID: <20080118114001.GA2610@ff.dom.local> References: <20080117203155.GA2791@ami.dom.local> <20080117232626.GC2905@ami.dom.local> <3ae72650801171755k85c4245i3b4c46a84ae8f52d@mail.gmail.com> <1200626323.5640.21.camel@lov.site> <20080118073836.GA1703@ff.dom.local> <1200653112.8706.21.camel@lov.site> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1200653112.8706.21.camel@lov.site> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2086 Lines: 48 On Fri, Jan 18, 2008 at 11:45:12AM +0100, Kay Sievers wrote: > On Fri, 2008-01-18 at 08:38 +0100, Jarek Poplawski wrote: > > On Fri, Jan 18, 2008 at 01:31:17PM +0800, Dave Young wrote: > > > On Jan 18, 2008 11:18 AM, Kay Sievers wrote: > > ... > > > > Yeah, might be better to wait until class_device is gone, otherwise you > > > > may need to fix stuff that is just going to be removed. Your change to > > > > have iterators for the class devices look like a nice preparation for > > > > future changes though. > > > > > > > > Our rough plan is: > > > > 2.6.25: > > > > - get the ~100 patches in Greg's tree (in -mm) merged :) > > > > 2.6.26: > > > > ??? - remove the 20 char limit in "struct device" > > > > - get rid of "struct class_device" > > > > > > Fine, thanks. > > > > > > Let's wait for other people's comment. > > > > Dave, I doubt you'll ever manage to do this if you're going to wait: > > probably there will be always some new changes like this around... > > Well there are not "changes" in that sense, the class_device stuff will > be entirely ripped out, and I doubt we will want to change anything > there, just shortly before it's deleted. So, 2.6.26 means shortly... And this all needs some time for testing, debugging or maybe some change of concept, so this would take a while... Well, it's not my problem, but since this stuff will go away, shouldn't we care more about the staff that will stay? > Also your assumptions about device nesting are not really true, there is > no limit, even when there are no current users nesting deeper, and > "struct device" can be any nesting depth, and that's where it gets > interesting. I'm just trying to figure this out. It seems this is a real problem while freezing, but not necessarily here (but I can miss something). Regards, Jarek P. -- 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/