be2net: Don't log "Out of MCCQ wrbs" error

Don't log "Out of MCCQ wrbs" msg. When the driver doesn't receive any
response from the FW it already logs a "FW not responding" message.
The driver runs out of MCCQ wrbs much later. Also, this message can
swamp the kernel log in HW/FW error scenarios.

Signed-off-by: Vasundhara Volam <vasundhara.volam@emulex.com>
Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/drivers/net/ethernet/emulex/benet/be_cmds.c b/drivers/net/ethernet/emulex/benet/be_cmds.c
index 5d96f773ea92ae559f036046708c7b5d58bf9b4b..a20b31d48a5ea2f4ad1482f3b2fcf23a7f3df6af 100644 (file)
--- a/drivers/net/ethernet/emulex/benet/be_cmds.c
+++ b/drivers/net/ethernet/emulex/benet/be_cmds.c
@@ -687,10 +687,8 @@ static struct be_mcc_wrb *wrb_from_mccq(struct be_adapter *adapter)
        if (!mccq->created)
                return NULL;
 
-       if (atomic_read(&mccq->used) >= mccq->len) {
-               dev_err(&adapter->pdev->dev, "Out of MCCQ wrbs\n");
+       if (atomic_read(&mccq->used) >= mccq->len)
                return NULL;
-       }
 
        wrb = queue_head_node(mccq);
        queue_head_inc(mccq);