[PATCH 0/4] [resend] n_tty fixes

From: Peter Hurley
Date: Sat Jun 15 2013 - 07:29:26 EST

On 03/19/2013 10:10 AM, Greg Kroah-Hartman wrote:> On Tue, Mar 19, 2013 at 09:57:09AM -0400, Peter Hurley wrote:
>> On Mon, 2013-03-18 at 16:15 -0700, Greg Kroah-Hartman wrote:
>>> On Wed, Mar 06, 2013 at 08:38:22AM -0500, Peter Hurley wrote:
>>>> minimum_to_wake is unique to N_TTY processing, and belongs in
>>>> per-ldisc data.
>>>> Add the ldisc method, ldisc_ops::fasync(), to notify line disciplines
>>>> when signal-driven I/O is enabled or disabled. When enabled for N_TTY
>>>> (by fcntl(F_SETFL, O_ASYNC)), blocking reader/polls will be woken
>>>> for any readable input. When disabled, blocking reader/polls are not
>>>> woken until the read buffer is full.
>>>> Canonical mode (L_ICANON(tty), n_tty_data::icanon) is not affected by
>>>> the minimum_to_wake setting.
>>>> Signed-off-by: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
>>> For some reason, this patch doesn't apply. Care to refresh this one,
>>> and the rest in this series, and resend?
>> Sorry. There was probably some accidental dependency on one of the other
>> patchsets of mine you did apply.
>> This and patch 5 now apply without error to tty-next.
> Ok, but they are now long gone from my queue. Can you please resend
> what I haven't applied?


I resent these back on 19 Mar but they never got applied. (maybe because
I resent them as 4,5,6 & 7/7 ??)

Anyway, these apply cleanly to tty-next.

Peter Hurley

Peter Hurley (4):
n_tty: Encapsulate minimum_to_wake within N_TTY
n_tty: Untangle read completion variables
n_tty: Fix unsafe update of available buffer space
n_tty: Buffer work should not reschedule itself

drivers/tty/n_tty.c | 76 ++++++++++++++++++++++++++++++-----------------
drivers/tty/tty_io.c | 17 ++++++-----
include/linux/tty.h | 1 -
include/linux/tty_ldisc.h | 6 ++++
4 files changed, 63 insertions(+), 37 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/