From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "Wang, Haiyue" <haiyue.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] common/iavf: update virtchnl
Date: Mon, 26 Apr 2021 07:46:37 +0000 [thread overview]
Message-ID: <MN2PR11MB3807AA665E08846FDB515321F7429@MN2PR11MB3807.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210424060337.2824837-1-qi.z.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Qi Z <qi.z.zhang@intel.com>
> Sent: Saturday, April 24, 2021 2:04 PM
> To: Xing, Beilei <beilei.xing@intel.com>
> Cc: Wang, Haiyue <haiyue.wang@intel.com>; dev@dpdk.org; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Subject: [PATCH 0/4] common/iavf: update virtchnl
>
> Couple code refine and bug fix
>
> Qi Zhang (4):
> common/iavf: fix duplicate defined offload bit
> common/iavf: add enumeration for the rxdid format
> common/iavf: refine comment in virtchnl
> common/iavf: use BIT() macro for offload/cap bits
>
> drivers/common/iavf/virtchnl.h | 183 ++++++++++++++++++++++++---------
> 1 file changed, 132 insertions(+), 51 deletions(-)
>
> --
> 2.26.2
Acked-by: Beilei Xing <beilei.xing@intel.com>
next prev parent reply other threads:[~2021-04-26 7:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 6:03 Qi Zhang
2021-04-24 6:03 ` [dpdk-dev] [PATCH 1/4] common/iavf: fix duplicate defined offload bit Qi Zhang
2021-04-24 6:03 ` [dpdk-dev] [PATCH 2/4] common/iavf: add enumeration for the rxdid format Qi Zhang
2021-04-24 6:03 ` [dpdk-dev] [PATCH 3/4] common/iavf: refine comment in virtchnl Qi Zhang
2021-04-24 6:03 ` [dpdk-dev] [PATCH 4/4] common/iavf: use BIT() macro for offload/cap bits Qi Zhang
2021-04-26 7:46 ` Xing, Beilei [this message]
2021-04-26 8:23 ` [dpdk-dev] [PATCH 0/4] common/iavf: update virtchnl Zhang, Qi Z
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=MN2PR11MB3807AA665E08846FDB515321F7429@MN2PR11MB3807.namprd11.prod.outlook.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@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).