From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <stable@dpdk.org>
Cc: Ivan Malov <ivan.malov@oktetlabs.ru>
Subject: [dpdk-stable] [PATCH 17.11] net/sfc: fix port ID log
Date: Mon, 11 Mar 2019 08:44:16 +0000 [thread overview]
Message-ID: <1552293856-24222-3-git-send-email-arybchenko@solarflare.com> (raw)
In-Reply-To: <1552293856-24222-1-git-send-email-arybchenko@solarflare.com>
From: Ivan Malov <ivan.malov@oktetlabs.ru>
[ backported from upstream commit 5a88b9b3f0ca0578779c3efad2e362c8770353b4 ]
Log port ID as 16-bit unsigned integer.
Fixes: f8244c6399d9 ("ethdev: increase port id range")
Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
---
drivers/net/sfc/sfc_log.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/sfc/sfc_log.h b/drivers/net/sfc/sfc_log.h
index b1a9df4..0c82b93 100644
--- a/drivers/net/sfc/sfc_log.h
+++ b/drivers/net/sfc/sfc_log.h
@@ -38,7 +38,8 @@
const struct sfc_adapter *__sa = (sa); \
\
RTE_LOG(level, PMD, \
- RTE_FMT("sfc_efx " PCI_PRI_FMT " #%" PRIu8 ": " \
+ RTE_FMT("PMD: sfc_efx " \
+ PCI_PRI_FMT " #%" PRIu16 \
RTE_FMT_HEAD(__VA_ARGS__,) "\n", \
__sa->pci_addr.domain, \
__sa->pci_addr.bus, \
--
1.8.3.1
next prev parent reply other threads:[~2019-03-11 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 8:44 [dpdk-stable] [PATCH 17.11] net/sfc: pass HW Tx queue index on creation Andrew Rybchenko
2019-03-11 8:44 ` [dpdk-stable] [PATCH 17.11] net/sfc/base: fix Tx descriptor max number check Andrew Rybchenko
2019-03-12 22:15 ` Yongseok Koh
2019-03-11 8:44 ` Andrew Rybchenko [this message]
2019-03-12 22:15 ` [dpdk-stable] [PATCH 17.11] net/sfc: fix port ID log Yongseok Koh
2019-03-12 22:15 ` [dpdk-stable] [PATCH 17.11] net/sfc: pass HW Tx queue index on creation Yongseok Koh
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=1552293856-24222-3-git-send-email-arybchenko@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=ivan.malov@oktetlabs.ru \
--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).