DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xing, Beilei" <beilei.xing@intel.com>
To: David Harton <dharton@cisco.com>, "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Zhang, Helin" <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: remove memset in i40evf_dev_info_get
Date: Thu, 28 Jun 2018 02:49:52 +0000	[thread overview]
Message-ID: <94479800C636CB44BD422CB454846E01321D0531@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20180628011538.2974-1-dharton@cisco.com>

Hi,

Thanks for the patch, but there's another patch which has been accepted for the issue.
https://patches.dpdk.org/patch/40682/

Best Regards,
Beilei

> -----Original Message-----
> From: David Harton [mailto:dharton@cisco.com]
> Sent: Thursday, June 28, 2018 9:16 AM
> To: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; David Harton <dharton@cisco.com>; Zhang, Helin
> <helin.zhang@intel.com>
> Subject: [PATCH] net/i40e: remove memset in i40evf_dev_info_get
> 
> i40evf_dev_info_get clears dev_info when data has already been set by the
> calling function. Remove the call to
> memset() to fix the problem.
> 
> Fixes: 4861cde46116 ("i40e: new poll mode driver")
> Cc: helin.zhang@intel.com
> 
> Signed-off-by: David Harton <dharton@cisco.com>
> ---
>  drivers/net/i40e/i40e_ethdev_vf.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/net/i40e/i40e_ethdev_vf.c
> b/drivers/net/i40e/i40e_ethdev_vf.c
> index 804e445..86b38d2 100644
> --- a/drivers/net/i40e/i40e_ethdev_vf.c
> +++ b/drivers/net/i40e/i40e_ethdev_vf.c
> @@ -2182,7 +2182,6 @@ i40evf_dev_info_get(struct rte_eth_dev *dev,
> struct rte_eth_dev_info *dev_info)  {
>  	struct i40e_vf *vf = I40EVF_DEV_PRIVATE_TO_VF(dev->data-
> >dev_private);
> 
> -	memset(dev_info, 0, sizeof(*dev_info));
>  	dev_info->max_rx_queues = vf->vsi_res->num_queue_pairs;
>  	dev_info->max_tx_queues = vf->vsi_res->num_queue_pairs;
>  	dev_info->min_rx_bufsize = I40E_BUF_SIZE_MIN;
> --
> 2.10.3.dirty

      reply	other threads:[~2018-06-28  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28  1:15 David Harton
2018-06-28  2:49 ` Xing, Beilei [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=94479800C636CB44BD422CB454846E01321D0531@SHSMSX101.ccr.corp.intel.com \
    --to=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=dharton@cisco.com \
    --cc=helin.zhang@intel.com \
    --cc=qi.z.zhang@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).