From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Sun, GuinanX" <guinanx.sun@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] fix MAC ctrl frame fwd get
Date: Sat, 23 May 2020 09:43:01 +0000 [thread overview]
Message-ID: <MWHPR11MB1391D7FF5993036340111802B7B50@MWHPR11MB1391.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200523052239.62928-1-guinanx.sun@intel.com>
Reviewed-by: Wei Zhao <wei.zhao1@intel.com>
> -----Original Message-----
> From: Sun, GuinanX <guinanx.sun@intel.com>
> Sent: Saturday, May 23, 2020 1:23 PM
> To: dev@dpdk.org
> Cc: Zhao1, Wei <wei.zhao1@intel.com>; Yang, Qiming
> <qiming.yang@intel.com>; Sun, GuinanX <guinanx.sun@intel.com>
> Subject: [PATCH v2 0/2] fix MAC ctrl frame fwd get
>
> Fix incorrect MAC control frame forward.
> Fix flow control status get.
> ---
> v2 changes:
> * Rebase.
> * Split into two patches.
> * Set fc mac_ctrl_frame_fwd by bit operation.
> * Modify commit messge.
>
> Guinan Sun (2):
> net/ixgbe: fix incorrect MAC control frame forward
> net/ixgbe: fix flow control status get
>
> drivers/net/ixgbe/ixgbe_ethdev.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-05-23 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 6:12 [dpdk-dev] [PATCH] net/ixgbe: delete MAC control frame fwd in struct adapter Guinan Sun
2020-05-22 7:46 ` Yang, Qiming
2020-05-22 9:42 ` Zhao1, Wei
2020-05-22 9:46 ` Zhao1, Wei
2020-05-23 2:35 ` Sun, GuinanX
2020-05-23 5:22 ` [dpdk-dev] [PATCH v2 0/2] fix MAC ctrl frame fwd get Guinan Sun
2020-05-23 5:22 ` [dpdk-dev] [PATCH v2 1/2] net/ixgbe: fix incorrect MAC control frame forward Guinan Sun
2020-05-23 5:22 ` [dpdk-dev] [PATCH v2 2/2] net/ixgbe: fix flow control status get Guinan Sun
2020-06-02 10:54 ` Jiang, YuX
2020-05-23 9:43 ` Zhao1, Wei [this message]
2020-07-20 9:56 ` [dpdk-dev] [PATCH v2 0/2] fix MAC ctrl frame fwd get Zhao1, Wei
2020-07-20 10:42 ` 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=MWHPR11MB1391D7FF5993036340111802B7B50@MWHPR11MB1391.namprd11.prod.outlook.com \
--to=wei.zhao1@intel.com \
--cc=dev@dpdk.org \
--cc=guinanx.sun@intel.com \
--cc=qiming.yang@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).