The patch titled drivers/isdn/i4l/isdn_tty.c: remove write_sem has been removed from the -mm tree. Its filename was drivers-isdn-i4l-isdn_ttyc-remove-write_sem.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: drivers/isdn/i4l/isdn_tty.c: remove write_sem From: Daniel Walker <dwalker@xxxxxxxxxx> I couldn't find any users, so removing it.. Signed-off-by: Daniel Walker <dwalker@xxxxxxxxxx> Cc: Karsten Keil <kkeil@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/isdn/i4l/isdn_tty.c | 1 - include/linux/isdn.h | 1 - 2 files changed, 2 deletions(-) diff -puN drivers/isdn/i4l/isdn_tty.c~drivers-isdn-i4l-isdn_ttyc-remove-write_sem drivers/isdn/i4l/isdn_tty.c --- a/drivers/isdn/i4l/isdn_tty.c~drivers-isdn-i4l-isdn_ttyc-remove-write_sem +++ a/drivers/isdn/i4l/isdn_tty.c @@ -1917,7 +1917,6 @@ isdn_tty_modem_init(void) info->owner = THIS_MODULE; #endif spin_lock_init(&info->readlock); - init_MUTEX(&info->write_sem); sprintf(info->last_cause, "0000"); sprintf(info->last_num, "none"); info->last_dir = 0; diff -puN include/linux/isdn.h~drivers-isdn-i4l-isdn_ttyc-remove-write_sem include/linux/isdn.h --- a/include/linux/isdn.h~drivers-isdn-i4l-isdn_ttyc-remove-write_sem +++ a/include/linux/isdn.h @@ -507,7 +507,6 @@ typedef struct modem_info { struct ktermios normal_termios; /* For saving termios structs */ struct ktermios callout_termios; wait_queue_head_t open_wait, close_wait; - struct semaphore write_sem; spinlock_t readlock; } modem_info; _ Patches currently in -mm which might be from dwalker@xxxxxxxxxx are origin.patch driver-base-memory-semaphore-to-mutex.patch usb-microtek-remove-unused-semaphore.patch usb-libusual-locking-cleanup.patch profile-likely-unlikely-macros.patch profile-likely-unlikely-macros-fix.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html