On Thu, May 03, 2012 at 10:24:08PM +0100, Alan Cox wrote: > From: Alan Cox <alan@xxxxxxxxxxxxxxx> > > In each remaining case the tty_lock is associated with a specific tty. This > means we can now lock on a per tty basis. We do need tty_lock_pair() for > the pty case. Uglier but still a step in the right direction. > > Signed-off-by: Alan Cox <alan@xxxxxxxxxxxxxxx> > Acked-by: Arnd Bergmann <arnd@xxxxxxxx> > --- > > drivers/tty/amiserial.c | 12 ++++---- > drivers/tty/cyclades.c | 2 + > drivers/tty/n_r3964.c | 11 ++++--- > drivers/tty/pty.c | 23 +++++++++------ > drivers/tty/synclink.c | 4 +-- > drivers/tty/synclink_gt.c | 4 +-- > drivers/tty/synclinkmp.c | 4 +-- > drivers/tty/tty_io.c | 67 +++++++++++++++++++++++++++------------------ > drivers/tty/tty_ldisc.c | 30 ++++++++++---------- > drivers/tty/tty_mutex.c | 60 ++++++++++++++++++++++++++++++---------- > drivers/tty/tty_port.c | 6 ++-- > include/linux/tty.h | 23 +++++++++------ > 12 files changed, 149 insertions(+), 97 deletions(-) You forgot the call in net/bluetooth/rfcomm/tty.c, I'll go fix that up... -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
