kernel: no need to check for active_block

The driver is not using the active_block but it fills data in the current_control. So, even if there is an allocation failure inside ZIO, this doesn't brake the driver. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

kernel: no need to check for active_block
The driver is not using the active_block but it fills data in the current_control. So, even if there is an allocation failure inside ZIO, this doesn't brake the driver. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
04264ec2 · Federico Vaga · 138e6c54 · 04264ec2
Commit 04264ec2 authored Apr 01, 2015 by Federico Vaga
Hide whitespace changes
Inline Side-by-side

Showing with 0 additions and 3 deletions

ft-irq.c kernel/ft-irq.c +0 -3

No files found.
--- a/kernel/ft-irq.c
+++ b/kernel/ft-irq.c
@@ -62,9 +62,6 @@ int ft_read_sw_fifo(struct fmctdc_dev *ft, int channel,

 	st = &ft->channels[channel - 1];

-	if (!chan->active_block)
-		return -EAGAIN;
-
 	ret = kfifo_out_spinlocked(&st->fifo, &ts,
 				   sizeof(struct ft_wr_timestamp), &ft->lock);
 	if (!ret) {