Prev: cpufreq: fix memory leak in cpufreq_add_dev
Next: [PATCH 4/4] add example files to the kernel sample directory
From: stefani on 20 Jul 2010 09:10 From: Stefani Seibold <stefani(a)seibold.net> User of the kernel fifo should never bypass the API and directly access the fifo structure. Otherwise it will be very hard to maintain the API. Signed-off-by: Stefani Seibold <stefani(a)seibold.net> --- drivers/char/nozomi.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/drivers/char/nozomi.c b/drivers/char/nozomi.c index a663800..d578449 100644 --- a/drivers/char/nozomi.c +++ b/drivers/char/nozomi.c @@ -1741,8 +1741,7 @@ static int ntty_write_room(struct tty_struct *tty) if (dc) { mutex_lock(&port->tty_sem); if (port->port.count) - room = port->fifo_ul.size - - kfifo_len(&port->fifo_ul); + room = kfifo_avail(&port->fifo_ul); mutex_unlock(&port->tty_sem); } return room; -- 1.7.1.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |