__tty_flush_buffer() is now only called by tty_flush_buffer();
merge functions.

Signed-off-by: Peter Hurley <[email protected]>
---
 drivers/tty/tty_buffer.c | 29 ++++++-----------------------
 1 file changed, 6 insertions(+), 23 deletions(-)

diff --git a/drivers/tty/tty_buffer.c b/drivers/tty/tty_buffer.c
index fb042b9..dbe4a71 100644
--- a/drivers/tty/tty_buffer.c
+++ b/drivers/tty/tty_buffer.c
@@ -151,28 +151,6 @@ static void tty_buffer_free(struct tty_port *port, struct 
tty_buffer *b)
 }
 
 /**
- *     __tty_buffer_flush              -       flush full tty buffers
- *     @tty: tty to flush
- *
- *     flush all the buffers containing receive data. Caller must
- *     hold the buffer lock and must have ensured no parallel flush to
- *     ldisc is running.
- */
-
-static void __tty_buffer_flush(struct tty_port *port)
-{
-       struct tty_bufhead *buf = &port->buf;
-       struct tty_buffer *next;
-
-       while ((next = buf->head->next) != NULL) {
-               tty_buffer_free(port, buf->head);
-               buf->head = next;
-       }
-       WARN_ON(buf->head != buf->tail);
-       buf->head->read = buf->head->commit;
-}
-
-/**
  *     tty_buffer_flush                -       flush full tty buffers
  *     @tty: tty to flush
  *
@@ -188,11 +166,16 @@ void tty_buffer_flush(struct tty_struct *tty)
 {
        struct tty_port *port = tty->port;
        struct tty_bufhead *buf = &port->buf;
+       struct tty_buffer *next;
 
        buf->flushpending = 1;
 
        mutex_lock(&buf->flush_mutex);
-       __tty_buffer_flush(port);
+       while ((next = buf->head->next) != NULL) {
+               tty_buffer_free(port, buf->head);
+               buf->head = next;
+       }
+       buf->head->read = buf->head->commit;
        buf->flushpending = 0;
        mutex_unlock(&buf->flush_mutex);
 }
-- 
1.8.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to