DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Sun, GuinanX" <guinanx.sun@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Guo, Jia" <jia.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] fix defects of macro in VF
Date: Fri, 8 May 2020 05:41:04 +0000	[thread overview]
Message-ID: <MWHPR11MB13913094483EDF3834FC87E2B7A20@MWHPR11MB1391.namprd11.prod.outlook.com> (raw)
In-Reply-To: <05758BDAD7FC8E4BAED63D0390A8A955847737@SHSMSX101.ccr.corp.intel.com>



> -----Original Message-----
> From: Sun, GuinanX <guinanx.sun@intel.com>
> Sent: Friday, May 8, 2020 1:07 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Cc: Guo, Jia <jia.guo@intel.com>
> Subject: RE: [dpdk-dev] [PATCH 0/2] fix defects of macro in VF
> 
> Hi ZhaoWei
> 
> > -----Original Message-----
> > From: Zhao1, Wei
> > Sent: Friday, May 8, 2020 10:19 AM
> > To: Sun, GuinanX <guinanx.sun@intel.com>; dev@dpdk.org
> > Cc: Sun, GuinanX <guinanx.sun@intel.com>; Guo, Jia <jia.guo@intel.com>
> > Subject: RE: [dpdk-dev] [PATCH 0/2] fix defects of macro in VF
> >
> > Hi,
> > Please alaign " \" in each line.
> 
> It will be modified in V2 patch.
> Remark: It can't be aligned in vim tool and email at the same time.
> It will be aligned in vim tool in v2 patch.
> 
> >

Ok.

> >
> > > -----Original Message-----
> > > From: dev <dev-bounces@dpdk.org> On Behalf Of Guinan Sun
> > > Sent: Friday, May 8, 2020 9:59 AM
> > > To: dev@dpdk.org
> > > Cc: Sun, GuinanX <guinanx.sun@intel.com>
> > > Subject: [dpdk-dev] [PATCH 0/2] fix defects of macro in VF
> > >
> > > The defects of UPDATE_VF_STAT and UPDATE_VF_STAT_36BIT exist.
> > > If latest is less than last, we will get wrong result.
> > > The issues exist only in ixgbe and e1000 NICs.
> > >
> > > Guinan Sun (2):
> > >   net/ixgbe: fix defects of macro in VF
> > >   net/e1000: fix defects of macro in VF
> > >
> > >  drivers/net/e1000/igb_ethdev.c   | 14 +++++++++++---
> > >  drivers/net/ixgbe/ixgbe_ethdev.c | 20 ++++++++++++++++++--
> > >  2 files changed, 29 insertions(+), 5 deletions(-)
> > >
> > > --
> > > 2.17.1
> >
> 


  reply	other threads:[~2020-05-08  5:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  1:59 Guinan Sun
2020-05-08  1:59 ` [dpdk-dev] [PATCH 1/2] net/ixgbe: " Guinan Sun
2020-05-08  1:59 ` [dpdk-dev] [PATCH 2/2] net/e1000: " Guinan Sun
2020-05-08  2:18 ` [dpdk-dev] [PATCH 0/2] " Zhao1, Wei
2020-05-08  5:07   ` Sun, GuinanX
2020-05-08  5:41     ` Zhao1, Wei [this message]
2020-05-08  4:46 ` [dpdk-dev] [PATCH v2 " Guinan Sun
2020-05-08  4:46   ` [dpdk-dev] [PATCH v2 1/2] net/ixgbe: " Guinan Sun
2020-05-08  4:46   ` [dpdk-dev] [PATCH v2 2/2] net/e1000: " Guinan Sun
2020-05-18  1:24     ` [dpdk-dev] [dpdk-stable] " Ye Xiaolong
2020-05-18  6:48       ` Zhao1, Wei
2020-05-18 23:39         ` Ye Xiaolong
2020-05-19  1:01           ` Zhao1, Wei
2020-05-18  7:21     ` [dpdk-dev] " Zhao1, Wei
2020-05-08  5:05   ` [dpdk-dev] [PATCH v2 0/2] " Zhao1, Wei
  -- strict thread matches above, loose matches on Subject: below --
2020-05-07  6:16 [dpdk-dev] [PATCH " Guinan Sun

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=MWHPR11MB13913094483EDF3834FC87E2B7A20@MWHPR11MB1391.namprd11.prod.outlook.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=guinanx.sun@intel.com \
    --cc=jia.guo@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).