DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chen, Jing D" <jing.d.chen@intel.com>
To: "Liu, Jijiang" <jijiang.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] i40e:fix an issue in i40e_dev_info_get
Date: Thu, 21 May 2015 01:50:43 +0000	[thread overview]
Message-ID: <4341B239C0EFF9468EE453F9E9F4604D016F34DF@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1432014939-29800-1-git-send-email-jijiang.liu@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jijiang Liu
> Sent: Tuesday, May 19, 2015 1:56 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] i40e:fix an issue in i40e_dev_info_get
> 
> To get device VMDQ info when only i40e VMDQ feature is enabled.
> 
> Signed-off-by: Jijiang Liu <jijiang.liu@intel.com>
> 
> ---
>  lib/librte_pmd_i40e/i40e_ethdev.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/lib/librte_pmd_i40e/i40e_ethdev.c
> b/lib/librte_pmd_i40e/i40e_ethdev.c
> index 96700e4..1faae83 100644
> --- a/lib/librte_pmd_i40e/i40e_ethdev.c
> +++ b/lib/librte_pmd_i40e/i40e_ethdev.c
> @@ -1565,7 +1565,7 @@ i40e_dev_info_get(struct rte_eth_dev *dev, struct
> rte_eth_dev_info *dev_info)
>  				ETH_TXQ_FLAGS_NOOFFLOADS,
>  	};
> 
> -	if (pf->flags | I40E_FLAG_VMDQ) {
> +	if (pf->flags & I40E_FLAG_VMDQ) {
>  		dev_info->max_vmdq_pools = pf->max_nb_vmdq_vsi;
>  		dev_info->vmdq_queue_base = dev_info->max_rx_queues;
>  		dev_info->vmdq_queue_num = pf->vmdq_nb_qps *
> --
> 1.7.7.6

Acked-by: Jing Chen <jing.d.chen@intel.com>

      parent reply	other threads:[~2015-05-21  1:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  5:55 Jijiang Liu
2015-05-21  1:15 ` Zhang, Helin
2015-05-29 18:10   ` Thomas Monjalon
2015-05-21  1:50 ` Chen, Jing D [this message]

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=4341B239C0EFF9468EE453F9E9F4604D016F34DF@shsmsx102.ccr.corp.intel.com \
    --to=jing.d.chen@intel.com \
    --cc=dev@dpdk.org \
    --cc=jijiang.liu@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).