[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <2ea0177d6d934934d26e7c988d5a57515da9e7b1.1544556206.git.jtoppins@redhat.com>
Date: Tue, 11 Dec 2018 14:23:26 -0500
From: Jonathan Toppins <jtoppins@...hat.com>
To: netdev@...r.kernel.org
Cc: michael.chan@...adcom.com
Subject: [PATCH net-next] bnxt: lower log priority of hwrm message to info
bnxt_en 0000:19:00.0 (unregistered net_device) (uninitialized): hwrm
req_type 0x190 seq id 0x6 error 0xffff
The message above is commonly seen when a newer driver is used on
hardware with older firmware. The issue is this message means nothing to
anyone except Broadcom. Reduce the message priority to info to not
confuse users as this message is really informative in nature.
Signed-off-by: Jonathan Toppins <jtoppins@...hat.com>
---
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
index 5d21c14853ac..796cb0b139dc 100644
--- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
+++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
@@ -3880,9 +3880,9 @@ static int bnxt_hwrm_do_send_msg(struct bnxt *bp, void *msg, u32 msg_len,
*valid = 0;
rc = le16_to_cpu(resp->error_code);
if (rc && !silent)
- netdev_err(bp->dev, "hwrm req_type 0x%x seq id 0x%x error 0x%x\n",
- le16_to_cpu(resp->req_type),
- le16_to_cpu(resp->seq_id), rc);
+ netdev_info(bp->dev, "hwrm req_type 0x%x seq id 0x%x error 0x%x\n",
+ le16_to_cpu(resp->req_type),
+ le16_to_cpu(resp->seq_id), rc);
return rc;
}
--
2.16.4
Powered by blists - more mailing lists