Prevent a kernel panic by avoiding the use of the BUG_ON macro.
Checkpatch detected this issue.

Signed-off-by: Laura Garcia Liebana <nev...@gmail.com>
---
Changes in v2:
        - According to Marc Dietrich, module creator, the WARN_ON macro is not 
needed as such cases shouldn't happen and they were introduced for debugging 
purposes.

 drivers/staging/nvec/nvec.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/staging/nvec/nvec.c b/drivers/staging/nvec/nvec.c
index c335ae2..f6a1dbb 100644
--- a/drivers/staging/nvec/nvec.c
+++ b/drivers/staging/nvec/nvec.c
@@ -641,11 +641,9 @@ static irqreturn_t nvec_interrupt(int irq, void *dev)
                        nvec_msg_free(nvec, nvec->rx);
                        nvec->state = 3;
                        nvec_tx_set(nvec);
-                       BUG_ON(nvec->tx->size < 1);
                        to_send = nvec->tx->data[0];
                        nvec->tx->pos = 1;
                } else if (status == (I2C_SL_IRQ)) {
-                       BUG_ON(nvec->rx == NULL);
                        nvec->rx->data[1] = received;
                        nvec->rx->pos = 2;
                        nvec->state = 4;
-- 
2.7.0

_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to