From: Julia Lawall Date: Tue, 6 Jul 2010 05:15:47 +0000 (-0700) Subject: forcedeth: correct valid flag X-Git-Tag: accepted/tizen/common/20141203.182822~10934^2~335 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=217d32dc5f299c483ca0d3c8cc6811c72c0339c4;p=platform%2Fkernel%2Flinux-arm64.git forcedeth: correct valid flag Elsewhere in the "optimized" functions, the "2" constants are used. NV_TX_VALID and NV_TX2_VALID have the same value. Signed-off-by: Julia Lawall Signed-off-by: David S. Miller --- diff --git a/drivers/net/forcedeth.c b/drivers/net/forcedeth.c index 268ea4d..9ef6a9d 100644 --- a/drivers/net/forcedeth.c +++ b/drivers/net/forcedeth.c @@ -2468,7 +2468,7 @@ static int nv_tx_done_optimized(struct net_device *dev, int limit) struct ring_desc_ex* orig_get_tx = np->get_tx.ex; while ((np->get_tx.ex != np->put_tx.ex) && - !((flags = le32_to_cpu(np->get_tx.ex->flaglen)) & NV_TX_VALID) && + !((flags = le32_to_cpu(np->get_tx.ex->flaglen)) & NV_TX2_VALID) && (tx_work < limit)) { dprintk(KERN_DEBUG "%s: nv_tx_done_optimized: flags 0x%x.\n",