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 3/6] net/liquidio: fix port id type
Date: Thu, 12 Oct 2017 17:32:49 +0800 [thread overview]
Message-ID: <20171012093252.53100-4-zhiyong.yang@intel.com> (raw)
In-Reply-To: <20171012093252.53100-1-zhiyong.yang@intel.com>
port_id in struct lio_device should be increased range to uint16_t since
port id in rte_eth_dev_data has already been defined as uint16_t.
Fixes: f8244c6399d9 ("ethdev: increase port id range")
Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
---
drivers/net/liquidio/lio_struct.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/liquidio/lio_struct.h b/drivers/net/liquidio/lio_struct.h
index 635e47fbf..10e3976af 100644
--- a/drivers/net/liquidio/lio_struct.h
+++ b/drivers/net/liquidio/lio_struct.h
@@ -684,7 +684,7 @@ struct lio_device {
uint8_t nb_tx_queues;
uint8_t port_configured;
struct lio_rss_ctx rss_state;
- uint8_t port_id;
+ uint16_t port_id;
char firmware_version[LIO_FW_VERSION_LENGTH];
};
#endif /* _LIO_STRUCT_H_ */
--
2.13.3
next prev parent reply other threads:[~2017-10-12 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 9:32 [dpdk-dev] [PATCH 0/6] " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 1/6] lib/librte_ether: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 2/6] net/bnxt: " Zhiyong Yang
2017-10-12 9:32 ` Zhiyong Yang [this message]
2017-10-12 9:32 ` [dpdk-dev] [PATCH 4/6] app/pdump: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 5/6] app/proc_info: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 6/6] app/testpmd: " Zhiyong Yang
2017-10-12 18:03 ` [dpdk-dev] [PATCH 0/6] " Ferruh Yigit
2017-10-12 20:12 ` Ferruh Yigit
2017-10-13 2:04 ` Yang, Zhiyong
2017-10-13 2:20 ` Ferruh Yigit
2017-10-13 2:31 ` Yang, Zhiyong
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=20171012093252.53100-4-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).