[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1360075250-21970-1-git-send-email-james.hogan@imgtec.com>
Date: Tue, 5 Feb 2013 14:40:48 +0000
From: James Hogan <james.hogan@...tec.com>
To: Jiri Slaby <jslaby@...e.cz>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: <linux-kernel@...r.kernel.org>,
James Hogan <james.hogan@...tec.com>
Subject: [PATCH 0/2] tty: metag_da: fix flipping after tty changes
The first patch fixes up tty/metag_da after Jiri's changes, "TTY: switch
tty_flip_buffer_push" and "TTY: convert more flipping functions",
switched tty_flip_buffer_push() and tty_prepare_flip_string() to take
tty_port rather than a tty_struct.
The second just refactors slightly as a result of it.
How is this sort of thing usually handled? I suppose either I squash it
into the original driver and base it on tty-next, move it into tty-next,
or just fix it up afterwards?
James Hogan (2):
tty: metag_da: update flip functions to use tty_port
tty: metag_da: avoid getting tty kref in dashtty_timer()
drivers/tty/metag_da.c | 36 +++++++++++++++++-------------------
1 files changed, 17 insertions(+), 19 deletions(-)
--
1.7.7.6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists