linux-kernel - Re: [PATCH 7/7] driver-core : convert semaphore to mutex in struct class

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Jan 2008 22:25:00 -0800
From:	Greg KH <gregkh@...e.de>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Dave Young <hidave.darkstar@...il.com>,
	Jarek Poplawski <jarkao2@...il.com>,
	Alan Stern <stern@...land.harvard.edu>,
	stefanr@...6.in-berlin.de, David Brownell <david-b@...bell.net>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 7/7] driver-core : convert semaphore to mutex in struct
	class

On Fri, Jan 18, 2008 at 04:18:43AM +0100, Kay Sievers wrote:
> On Fri, 2008-01-18 at 10:28 +0800, Dave Young wrote:
> > Then what's your opinon about the lockdep warning fix? I wonder
> > whether the "soon" means we should do mutex convert after the
> > class_device going away?
> 
> 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"
>  2.6.27
>   - merge most of "struct class" and "struct bus_type" and have
>     only one type of list and iterator for all devices of all subsystems
>  2.6.27+
>   - allow multiple "drivers" to bind a single device (now that the
>     difference between class and bus devices is gone)

I'm hoping that we might be able to get this last one by 2.6.26 or .27,
depending on how much time I get to work on it...

Other than that, I agree with this timeline.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/