From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] iavf share code update
Date: Fri, 10 Apr 2020 00:42:21 +0000 [thread overview]
Message-ID: <BYAPR11MB35419D02817F9EF5534ED41AF7DE0@BYAPR11MB3541.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200410003444.16704-1-qi.z.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Qi Z <qi.z.zhang@intel.com>
> Sent: Friday, April 10, 2020 8:35 AM
> To: Xing, Beilei <beilei.xing@intel.com>
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Ye, Xiaolong
> <xiaolong.ye@intel.com>; dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: [PATCH 0/6] iavf share code update
>
> Update virtual channel to support
> 1) DDP package info query
> 2) flexibale RXID negotiate
> 3) RSS and FDIR
>
> Qi Zhang (6):
> common/iavf: add PTYPE definition
> common/iavf: add DDP package query in virtual channel
> common/iavf: add virtual channel support for Flex RXD
> common/iavf: add virtual channel protocol header
> common/iavf: add advanced RSS input set change support
> common/iavf: add flow director support in virtual channel
>
> drivers/common/iavf/iavf_type.h | 3 +-
> drivers/common/iavf/virtchnl.h | 380
> +++++++++++++++++++++++++++++++++++++++-
> 2 files changed, 380 insertions(+), 3 deletions(-)
>
> --
> 2.13.6
Acked-by: Beilei Xing <beilei.xing@intel.com>
prev parent reply other threads:[~2020-04-10 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 0:34 Qi Zhang
2020-04-10 0:42 ` 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=BYAPR11MB35419D02817F9EF5534ED41AF7DE0@BYAPR11MB3541.namprd11.prod.outlook.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=xiaolong.ye@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).