net: bcmgenet: Use BUG_ON instead of if condition followed by BUG
Subsystems (3)
PATCH 1/1 net: bcmgenet: Use BUG_ON instead of if condition followed by BUG
Use BUG_ON instead of if condition followed by BUG.
Something to notice in this particular case is that unlikely() is already being called inside BUG_ON macro.
This issue was detected with the help of Coccinelle.
Signed-off-by Gustavo A. R. Silva <[email protected]>
--- drivers/net/ethernet/broadcom/genet/bcmgenet.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/net/ethernet/broadcom/genet/bcmgenet.c +1 -2
@@ -1584,8 +1584,7 @@ static netdev_tx_t bcmgenet_xmit(struct sk_buff *skb, struct net_device *dev)for (i =0 ; i <= nr_frags; i++) { tx_cb_ptr =bcmgenet_get_txcb (priv, ring); -if (unlikely (!tx_cb_ptr)) -BUG (); +BUG_ON (!tx_cb_ptr);if (!i) {/* Transmit single SKB or head of fragment list */
Signature · 1 line
2.7.4
From: "Gustavo A. R. Silva" <[email protected]>
Date: Thu, 26 Oct 2017 07:16:01 -0500
Quoted 8 lines
Use
BUG_ONinstead of if condition followed by BUG.Something to notice in this particular case is that
unlikely()is already being called insideBUG_ONmacro.This issue was detected with the help of Coccinelle.
Signed-off-by Gustavo A. R. Silva <[email protected]>
Applied.