linux-kernel - [PATCH] Char: nozomi, use tty

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat,  7 Oct 2006 01:27:07 +0200 (CEST)
From:	Jiri Slaby <jirislaby@...il.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: [PATCH] Char: nozomi, use tty_wakeup

nozomi, use tty_wakeup

Use tty_wakeup instead of self-implemented wake calling.

Cc: Alan Cox <alan@...rguk.ukuu.org.uk>
Signed-off-by: Jiri Slaby <jirislaby@...il.com>

---
commit b19884f570ea41ff9100cc56962e8d6f435e2337
tree f68d0e40ee5e527a0c6d96dc28291235032c45e1
parent 56269f9ba9ccaf60a314ebcf58d4de650995c4e5
author Jiri Slaby <jirislaby@...il.com> Sat, 07 Oct 2006 01:23:24 +0200
committer Jiri Slaby <xslaby@...moi.localdomain> Sat, 07 Oct 2006 01:23:24 +0200

 drivers/char/nozomi.c |    8 ++------
 1 files changed, 2 insertions(+), 6 deletions(-)

diff --git a/drivers/char/nozomi.c b/drivers/char/nozomi.c
index cd95ed5..8d502d2 100644
--- a/drivers/char/nozomi.c
+++ b/drivers/char/nozomi.c
@@ -922,12 +922,8 @@ static int send_data( enum port_type ind
     SET_MEM( addr, &size, 4 );
     SET_MEM_BUF( addr + 4, dc->send_buf, size);
 
-    if (port->tty) {
-        if ((tty->flags & (1 << TTY_DO_WRITE_WAKEUP)) && tty->ldisc.write_wakeup) {
-            tty->ldisc.write_wakeup(tty);
-        }
-        wake_up_interruptible(&tty->write_wait);
-    }
+    if (tty)
+	tty_wakeup(tty);
 
     return 1;
 }
-
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/