diff options
author | Anton Ivanov <anton.ivanov@cambridgegreys.com> | 2018-11-13 15:08:02 +0000 |
---|---|---|
committer | Richard Weinberger <richard@nod.at> | 2018-12-27 22:48:35 +0100 |
commit | 940b241d9050fc354f68c182e99fc3da1ff36bc0 (patch) | |
tree | d57775381213bb7cf168bc506242e054954e6e5c /arch/um/drivers/line.c | |
parent | b9794231737ab8c8a3a225b50aa168c4c7f9b9ec (diff) | |
download | linux-940b241d9050fc354f68c182e99fc3da1ff36bc0.tar.bz2 |
um: Remove obsolete reenable_XX calls
reenable_fd has been a NOP since the introduction of the EPOLL
based interrupt controller.
reenable_channel() is no longer needed as the flow control is
now handled via the write IRQs on the channel.
Signed-off-by: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'arch/um/drivers/line.c')
-rw-r--r-- | arch/um/drivers/line.c | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/arch/um/drivers/line.c b/arch/um/drivers/line.c index 7e524efed584..e0e63931fb2b 100644 --- a/arch/um/drivers/line.c +++ b/arch/um/drivers/line.c @@ -235,14 +235,6 @@ void line_unthrottle(struct tty_struct *tty) line->throttled = 0; chan_interrupt(line, line->driver->read_irq); - - /* - * Maybe there is enough stuff pending that calling the interrupt - * throttles us again. In this case, line->throttled will be 1 - * again and we shouldn't turn the interrupt back on. - */ - if (!line->throttled) - reactivate_chan(line->chan_in, line->driver->read_irq); } static irqreturn_t line_write_interrupt(int irq, void *data) @@ -667,8 +659,6 @@ static irqreturn_t winch_interrupt(int irq, void *data) tty_kref_put(tty); } out: - if (winch->fd != -1) - reactivate_fd(winch->fd, WINCH_IRQ); return IRQ_HANDLED; } |