Dave Young wrote: > Convert semaphore to mutex in struct class. > All the patches in this series should be applyed simultaneously Therefore you eventually need to repost it as a single patch. It can't go into one of the maintainer trees otherwise, because they only take fully bijectable patches. (Kernel must build and run at any point in between any patch series.) > toc: > --- > 1-driver-core-struct-class-convert-semaphore-to-mutex.patch > 2-i2c-struct-class-convert-semaphore-to-mutex.patch > 3-ieee1394-struct-class-convert-semaphore-to-mutex.patch > 4-power-struct-class-convert-semaphore-to-mutex.patch > 5-rtc-struct-class-convert-semaphore-to-mutex.patch > 6-scsi-struct-class-convert-semaphore-to-mutex.patch > 7-spi-struct-class-convert-semaphore-to-mutex.patch I was going to test it at runtime on top of 2.6.24-rc6, but the first and second patch depend on stuff in -mm. So, my laziness wins for now, as -mm is not my cup of tea. About your changelog: "xyz: convert semaphore to mutex in struct class Use mutex instead of semaphore in struct class. Signed-off-by: Dave Young <hidave.darkstar@xxxxxxxxx>" You don't need the second line because it says the same as the first line. Either kill it, or replace it by an explanation _why_ the semaphore is to be replaced by mutex. (I guess you do it because they are lighter-weight, both in semantics and in implementation, and because there are better facilities to debug mutexes...) -- Stefan Richter -=====-==--- ---= --==- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
