[PATCH 00/15] Staging: Convert the semaphore mess

From: John Kacur
Date: Mon Jan 11 2010 - 15:54:38 EST


Thomas / Ingo / Greg

I started with the patch in -rt 041e3130496f31d0cb4887fc6183117e662f5141
and tried to forward port it to 2.6.33-rc3

The patch no-longer applied, because some of the changes were already accepted
upstream, some files had been moved or dropped and so on.

So, I broke the original patch into one patch per file, and fixed merge errors.
Then I also went and changed similar problems in new code

This code should be queued-up for the 2.6.34 merge window, and should also
be applied to the latests -rt branch.

John Kacur (6):
mt9d112: Convert the semaphore mess.
mt9p012_fox: Convert the semaphore mess
mt9t013: Convert the semaphore mess
s5k3e2fx: Convert the semaphore mess
pmem: Convert the semaphore mess.
vme_user: Convert the semaphore mess

Thomas Gleixner (9):
dt9812: Convert the semaphore mess
usbdux.c: Convert the semaphore mess
usbduxfast: Convert the semaphore mess
alphatrack: Convert the semaphore mess
tranzport: Convert he semaphore mess
mimio: Convert semaphore mess
wwrap: Convert the semaphore mess
p9auth: Convert the semaphore mess
rtmp_init: Convert the semaphore mess.

drivers/staging/comedi/drivers/dt9812.c | 4 ++--
drivers/staging/comedi/drivers/usbdux.c | 4 ++--
drivers/staging/comedi/drivers/usbduxfast.c | 4 ++--
drivers/staging/dream/camera/mt9d112.c | 2 +-
drivers/staging/dream/camera/mt9p012_fox.c | 2 +-
drivers/staging/dream/camera/mt9t013.c | 2 +-
drivers/staging/dream/camera/s5k3e2fx.c | 2 +-
drivers/staging/dream/pmem.c | 2 +-
drivers/staging/frontier/alphatrack.c | 2 +-
drivers/staging/frontier/tranzport.c | 4 ++--
drivers/staging/mimio/mimio.c | 2 +-
drivers/staging/otus/wwrap.c | 2 +-
drivers/staging/p9auth/p9auth.c | 2 +-
drivers/staging/rt2860/common/rtmp_init.c | 2 +-
drivers/staging/vme/devices/vme_user.c | 2 +-
15 files changed, 19 insertions(+), 19 deletions(-)

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