From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Cc: "Mody, Rasesh" <Rasesh.Mody@cavium.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: [dpdk-stable] [PATCH 18.08] net/bnx2x: fix info logs backport
Date: Wed, 23 Jan 2019 22:33:23 +0000 [thread overview]
Message-ID: <1548282791-10600-1-git-send-email-rasesh.mody@cavium.com> (raw)
This patch fixes build failure introduced by following commit.
Fixes: 8570d267a87e ("net/bnx2x: cleanup info logs")
Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
---
drivers/net/bnx2x/bnx2x.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/net/bnx2x/bnx2x.c b/drivers/net/bnx2x/bnx2x.c
index c80f84c..a726742 100644
--- a/drivers/net/bnx2x/bnx2x.c
+++ b/drivers/net/bnx2x/bnx2x.c
@@ -6918,19 +6918,19 @@ static void bnx2x_link_report_locked(struct bnx2x_softc *sc)
return;
}
- ELINK_DEBUG_P2(sc, "Change in link status : cur_data = %lx, last_reported_link = %lx",
+ PMD_DRV_LOG(DEBUG, sc, "Change in link status : cur_data = %lx, last_reported_link = %lx",
cur_data.link_report_flags,
sc->last_reported_link.link_report_flags);
sc->link_cnt++;
- ELINK_DEBUG_P1(sc, "link status change count = %x", sc->link_cnt);
+ PMD_DRV_LOG(DEBUG, sc, "link status change count = %x", sc->link_cnt);
/* report new link params and remember the state for the next time */
rte_memcpy(&sc->last_reported_link, &cur_data, sizeof(cur_data));
if (bnx2x_test_bit(BNX2X_LINK_REPORT_LINK_DOWN,
&cur_data.link_report_flags)) {
- ELINK_DEBUG_P0(sc, "NIC Link is Down");
+ PMD_DRV_LOG(DEBUG, sc, "NIC Link is Down");
} else {
__rte_unused const char *duplex;
__rte_unused const char *flow;
@@ -6938,10 +6938,10 @@ static void bnx2x_link_report_locked(struct bnx2x_softc *sc)
if (bnx2x_test_and_clear_bit(BNX2X_LINK_REPORT_FULL_DUPLEX,
&cur_data.link_report_flags)) {
duplex = "full";
- ELINK_DEBUG_P0(sc, "link set to full duplex");
+ PMD_DRV_LOG(DEBUG, sc, "link set to full duplex");
} else {
duplex = "half";
- ELINK_DEBUG_P0(sc, "link set to half duplex");
+ PMD_DRV_LOG(DEBUG, sc, "link set to half duplex");
}
/*
--
1.7.10.3
next reply other threads:[~2019-01-23 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 22:33 Mody, Rasesh [this message]
2019-01-30 17:17 ` Kevin Traynor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1548282791-10600-1-git-send-email-rasesh.mody@cavium.com \
--to=rasesh.mody@cavium.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).