From: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
To: Rami Rosen <rami.rosen@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH dpdk-next-net] net/axgbe: fix an assignment error in axgbe_dev_info_get()
Date: Mon, 9 Apr 2018 13:56:15 +0000 [thread overview]
Message-ID: <CY4PR12MB15099F205035089E59078B62AEBF0@CY4PR12MB1509.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20180409201843.2317-1-rami.rosen@intel.com>
>This patch fixes a tirvial error in assigning max Rx/Tx queues in axgbe_dev_info_get() of the axgbe PMD driver.
>
>Signed-off-by: Rami Rosen <rami.rosen@intel.com>
>---
> drivers/net/axgbe/axgbe_ethdev.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/net/axgbe/axgbe_ethdev.c b/drivers/net/axgbe/axgbe_ethdev.c
>index 07c1337ac..a9a9fb570 100644
>--- a/drivers/net/axgbe/axgbe_ethdev.c
>+++ b/drivers/net/axgbe/axgbe_ethdev.c
>@@ -355,8 +355,8 @@ axgbe_dev_info_get(struct rte_eth_dev *dev,
> struct axgbe_port *pdata = dev->data->dev_private;
>
> dev_info->pci_dev = RTE_ETH_DEV_TO_PCI(dev);
>- dev_info->max_rx_queues = pdata->tx_ring_count;
>- dev_info->max_tx_queues = pdata->rx_ring_count;
>+ dev_info->max_rx_queues = pdata->rx_ring_count;
>+ dev_info->max_tx_queues = pdata->tx_ring_count;
> dev_info->min_rx_bufsize = AXGBE_RX_MIN_BUF_SIZE;
> dev_info->max_rx_pktlen = AXGBE_RX_MAX_BUF_SIZE;
> dev_info->max_mac_addrs = AXGBE_MAX_MAC_ADDRS;
>--
>2.14.3
>
Thanks a lot Remi. Wonderful catch.
Regards,
Ravi
next prev parent reply other threads:[~2018-04-09 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 20:18 Rami Rosen
2018-04-09 13:56 ` Kumar, Ravi1 [this message]
2018-04-09 14:02 ` Ferruh Yigit
2018-04-12 18:02 ` 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=CY4PR12MB15099F205035089E59078B62AEBF0@CY4PR12MB1509.namprd12.prod.outlook.com \
--to=ravi1.kumar@amd.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=rami.rosen@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).