Commit 2c590f3c authored by Tejun Heo's avatar Tejun Heo Committed by Greg Kroah-Hartman

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: default avatarTejun Heo <tj@kernel.org>
Cc: Jiri Slaby <jslaby@suse.cz>
Cc: Alan Cox <alan@linux.intel.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent 8c6e9112
...@@ -1514,8 +1514,6 @@ static void __devexit tty_exit(struct nozomi *dc) ...@@ -1514,8 +1514,6 @@ static void __devexit tty_exit(struct nozomi *dc)
DBG1(" "); DBG1(" ");
flush_scheduled_work();
for (i = 0; i < MAX_PORT; ++i) { for (i = 0; i < MAX_PORT; ++i) {
struct tty_struct *tty = tty_port_tty_get(&dc->port[i].port); struct tty_struct *tty = tty_port_tty_get(&dc->port[i].port);
if (tty && list_empty(&tty->hangup_work.entry)) if (tty && list_empty(&tty->hangup_work.entry))
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment