Re: No big TTY/serial patch merge for 3.6-rc1
From: Greg KH
Date: Thu Jul 26 2012 - 17:28:07 EST
On Thu, Jul 26, 2012 at 10:23:13PM +0100, Alan Cox wrote:
> On Thu, 26 Jul 2012 12:08:14 -0700
> Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>
> > tty: Move the handling of the tty release logic
>
> Can we lose that one specifically. I've chased down Ian Abbotts problem
> and replicated it and that is the offending patch not the lock localise
> (which still needs to be kept out as it depends upon this one)
>
> I have it fixed but it's not had enough testing for -rc1 and moving the
> termios data has enough spectacular hits all drivers fallout for 3.6
Yes, I can go revert it. I'm working on building up a small tty-linus
branch at the moment for just the "must haves" for 3.6. Right now it's
just 10 patches listed below. Any objection to me sending these after
a round trip through linux-next?
thanks,
greg k-h
.../devicetree/bindings/tty/serial/of-serial.txt | 1 +
drivers/tty/serial/8250/8250.c | 8 +++
drivers/tty/serial/of_serial.c | 1 +
drivers/tty/serial/pch_uart.c | 59 +++++++++++++-------
drivers/tty/serial/samsung.c | 4 +-
drivers/tty/serial/serial_core.c | 6 +-
drivers/tty/tty_ldisc.c | 2 +-
drivers/tty/vt/vt_ioctl.c | 47 +++++++++++-----
include/linux/serial_core.h | 3 +-
9 files changed, 93 insertions(+), 38 deletions(-)
---------------
Alan Cox (1):
pch_uart: Fix missing break for 16 byte fifo
Corbin (1):
serial_core: Update buffer overrun statistics.
Darren Hart (1):
pch_uart: Add eg20t_port lock field, avoid recursive spinlocks
Kyoungil Kim (1):
serial: samsung: Fixed wrong comparison for baudclk_rate
Rabin Vincent (1):
vt: fix race in vt_waitactive()
Roland Stigge (2):
serial/8250: Add LPC3220 standard UART type
serial/of-serial: Add LPC3220 standard UART compatible string
Shachar Shemesh (1):
tty ldisc: Close/Reopen race prevention should check the proper flag
Tomoya MORINAGA (2):
pch_uart: Fix rx error interrupt setting issue
pch_uart: Fix parity setting issue
--
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/