From: Zhiyong Yang <zhiyong.yang@intel.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, Zhiyong Yang <zhiyong.yang@intel.com>
Subject: [dpdk-dev] [PATCH 1/8] net/bonding: fix port id type
Date: Fri, 13 Oct 2017 21:16:54 +0800 [thread overview]
Message-ID: <20171013131701.38147-2-zhiyong.yang@intel.com> (raw)
In-Reply-To: <20171013131701.38147-1-zhiyong.yang@intel.com>
Fixes: f8244c6399d9 ("ethdev: increase port id range")
Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
---
drivers/net/bonding/rte_eth_bond_pmd.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c b/drivers/net/bonding/rte_eth_bond_pmd.c
index 8cbcf6d72..3fbc1b123 100644
--- a/drivers/net/bonding/rte_eth_bond_pmd.c
+++ b/drivers/net/bonding/rte_eth_bond_pmd.c
@@ -538,7 +538,7 @@ ipv4_addr_to_dot(uint32_t be_ipv4_addr, char *buf, uint8_t buf_size)
#define MAX_CLIENTS_NUMBER 128
uint8_t active_clients;
struct client_stats_t {
- uint8_t port;
+ uint16_t port;
uint32_t ipv4_addr;
uint32_t ipv4_rx_packets;
uint32_t ipv4_tx_packets;
@@ -546,7 +546,7 @@ struct client_stats_t {
struct client_stats_t client_stats[MAX_CLIENTS_NUMBER];
static void
-update_client_stats(uint32_t addr, uint8_t port, uint32_t *TXorRXindicator)
+update_client_stats(uint32_t addr, uint16_t port, uint32_t *TXorRXindicator)
{
int i = 0;
@@ -604,7 +604,7 @@ update_client_stats(uint32_t addr, uint8_t port, uint32_t *TXorRXindicator)
static void
mode6_debug(const char __attribute__((unused)) *info, struct ether_hdr *eth_h,
- uint8_t port, uint32_t __attribute__((unused)) *burstnumber)
+ uint16_t port, uint32_t __attribute__((unused)) *burstnumber)
{
struct ipv4_hdr *ipv4_h;
#ifdef RTE_LIBRTE_BOND_DEBUG_ALB
@@ -2059,7 +2059,7 @@ bond_ethdev_close(struct rte_eth_dev *dev)
RTE_LOG(INFO, EAL, "Closing bonded device %s\n", dev->device->name);
while (internals->slave_count != skipped) {
- uint8_t port_id = internals->slaves[skipped].port_id;
+ uint16_t port_id = internals->slaves[skipped].port_id;
rte_eth_dev_stop(port_id);
--
2.13.3
next prev parent reply other threads:[~2017-10-13 13:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 13:16 [dpdk-dev] [PATCH 0/8] " Zhiyong Yang
2017-10-13 13:16 ` Zhiyong Yang [this message]
2017-10-13 13:16 ` [dpdk-dev] [PATCH 2/8] net/i40e: " Zhiyong Yang
2017-10-13 13:16 ` [dpdk-dev] [PATCH 3/8] net/fm10k: " Zhiyong Yang
2017-10-13 13:16 ` [dpdk-dev] [PATCH 4/8] net/mrvl: " Zhiyong Yang
2017-10-13 13:16 ` [dpdk-dev] [PATCH 5/8] app: " Zhiyong Yang
2017-10-13 13:16 ` [dpdk-dev] [PATCH 6/8] test: " Zhiyong Yang
2017-10-13 13:17 ` [dpdk-dev] [PATCH 7/8] examples: " Zhiyong Yang
2017-10-13 13:17 ` [dpdk-dev] [PATCH 8/8] doc: update " Zhiyong Yang
2017-10-13 15:41 ` Mcnamara, John
2017-10-16 1:32 ` Yang, Zhiyong
2017-10-18 9:13 ` Van Haaren, Harry
2017-10-13 18:25 ` [dpdk-dev] [PATCH 0/8] fix " Ferruh Yigit
2017-10-13 18:26 ` Ferruh Yigit
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=20171013131701.38147-2-zhiyong.yang@intel.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).