[PATCH] nozomi: don't use flush_scheduled_work()

From: Tejun Heo
Date: Mon Jan 24 2011 - 11:55:14 EST


flush_scheduled_work() in tty_exit() doesn't seem to target any
specific work. If it was to flush work items used in tty generic
layer, they're already flushed properly during tty release.

flush_scheduled_work() is going away. Remove the seemingly redundant
usage.

Signed-off-by: Tejun Heo <tj@xxxxxxxxxx>
Cc: Jiri Slaby <jslaby@xxxxxxx>
Cc: Alan Cox <alan@xxxxxxxxxxxxxxx>
Cc: Greg Kroah-Hartman <gregkh@xxxxxxx>
---
drivers/char/nozomi.c | 2 --
1 file changed, 2 deletions(-)

Index: work/drivers/char/nozomi.c
===================================================================
--- work.orig/drivers/char/nozomi.c
+++ work/drivers/char/nozomi.c
@@ -1514,8 +1514,6 @@ static void __devexit tty_exit(struct no

DBG1(" ");

- flush_scheduled_work();
-
for (i = 0; i < MAX_PORT; ++i) {
struct tty_struct *tty = tty_port_tty_get(&dc->port[i].port);
if (tty && list_empty(&tty->hangup_work.entry))
--
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/