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
| ||
|
Date: Mon, 7 Jan 2008 18:00:36 +0800 From: "Dave Young" <hidave.darkstar@...il.com> To: "Greg KH" <gregkh@...e.de> Cc: "Stefan Richter" <stefanr@...6.in-berlin.de>, stern@...land.harvard.edu, peterz@...radead.org, david-b@...bell.net, davem@...emloft.net, jarkao2@...il.com, krh@...hat.com, dbrownell@...rs.sourceforge.net, James.Bottomley@...senpartnership.com, a.zummo@...ertech.it, cbou@...l.ru, dwmw2@...radead.org, linux1394-devel@...ts.sourceforge.net, spi-devel-general@...ts.sourceforge.net, linux-scsi@...r.kernel.org, rtc-linux@...glegroups.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/7] convert semaphore to mutex in struct class On Jan 7, 2008 4:45 PM, Greg KH <gregkh@...e.de> wrote: > On Mon, Jan 07, 2008 at 10:09:44AM +0800, Dave Young wrote: > > > > Thanks for your comment, I rewrite it for 2.6.24-rc7 as a all-in-one > > patch, please see following. Drop i2c maintainer and list in cc > > because there's no changes about i2c in this patch: > > > > Convert semaphore to mutex in struct class > > Most of the non-driver core code should be converted to not use the > lock in the class at all. They should use a local lock instead. > > So how about a patch series that removes the usage of the current > semaphore from the different drivers, and then, a single patch that > converts the semaphore to mutex in the class code, it should not touch > anything outside of the drivers/base/ directory (not including the > driver.h file.) > > Sound reasonable? looks like a better aproach, let me take a look ... > > 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/
Powered by blists - more mailing lists