The patch titled
drivers/char/tty_io.c: remove pty_sem
has been removed from the -mm tree. Its filename was
drivers-char-tty_ioc-remove-pty_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/char/tty_io.c: remove pty_sem
From: Daniel Walker <[EMAIL PROTECTED]>
I couldn't find any users, so removing it..
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Cc: "H. Peter Anvin" <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
drivers/char/tty_io.c | 1 -
include/linux/tty.h | 1 -
2 files changed, 2 deletions(-)
diff -puN drivers/char/tty_io.c~drivers-char-tty_ioc-remove-pty_sem
drivers/char/tty_io.c
--- a/drivers/char/tty_io.c~drivers-char-tty_ioc-remove-pty_sem
+++ a/drivers/char/tty_io.c
@@ -3721,7 +3721,6 @@ static void initialize_tty_struct(struct
tty->buf.head = tty->buf.tail = NULL;
tty_buffer_init(tty);
INIT_DELAYED_WORK(&tty->buf.work, flush_to_ldisc);
- init_MUTEX(&tty->buf.pty_sem);
mutex_init(&tty->termios_mutex);
init_waitqueue_head(&tty->write_wait);
init_waitqueue_head(&tty->read_wait);
diff -puN include/linux/tty.h~drivers-char-tty_ioc-remove-pty_sem
include/linux/tty.h
--- a/include/linux/tty.h~drivers-char-tty_ioc-remove-pty_sem
+++ a/include/linux/tty.h
@@ -74,7 +74,6 @@ struct tty_buffer {
struct tty_bufhead {
struct delayed_work work;
- struct semaphore pty_sem;
spinlock_t lock;
struct tty_buffer *head; /* Queue head */
struct tty_buffer *tail; /* Active buffer */
_
Patches currently in -mm which might be from [EMAIL PROTECTED] 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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html