From: Tejun Heo <tj@kernel.org>
Date: Mon, 24 Jan 2011 16:54:48 +0000 (+0100)
Subject: nozomi: don't use flush_scheduled_work()
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=2c590f3ca99c193a04fe90ec89046138b66fcc1e;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git

nozomi: don't use flush_scheduled_work()

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@kernel.org>
Cc: Jiri Slaby <jslaby@suse.cz>
Cc: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---

diff --git a/drivers/tty/nozomi.c b/drivers/tty/nozomi.c
index 513ba12064ea..f4f11164efe5 100644
--- a/drivers/tty/nozomi.c
+++ b/drivers/tty/nozomi.c
@@ -1514,8 +1514,6 @@ static void __devexit tty_exit(struct nozomi *dc)
 
 	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))