From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kevin Traynor <ktraynor@redhat.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/i40e: fix flow control watermark mismatch
Date: Fri, 18 Aug 2017 15:35:18 +0100 [thread overview]
Message-ID: <4c8eace2-22ce-f569-30b2-e17825a19cca@intel.com> (raw)
In-Reply-To: <94a7b3a7-a3d8-6d67-52ab-2c3595e4b302@redhat.com>
On 8/15/2017 6:40 PM, Kevin Traynor wrote:
> On 08/13/2017 01:05 AM, Zhang, Qi Z wrote:
>> Hi Kevin:
>>
>>> -----Original Message-----
>>> From: Kevin Traynor [mailto:ktraynor@redhat.com]
>>> Sent: Thursday, August 10, 2017 11:16 PM
>>> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>
>>> Cc: dev@dpdk.org; stable@dpdk.org
>>> Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix flow control watermark
>>> mismatch
>>>
>>> On 08/10/2017 11:48 AM, Qi Zhang wrote:
>>>> Flow control watermark is not read out correctly, that may cause an
>>>> application who not intend to change watermark but does change it with
>>>> a rte_eth_dev_flow_ctrl_set call right after
>>>> rte_eth_dev_flow_ctrl_get.
>>>>
>>>> Fixes: f53577f06925 ("i40e: support flow control")
>>>> Cc: stable@dpdk.org
>>>>
>>>> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> Acked-by: Kevin Traynor <ktraynor@redhat.com>
Applied to dpdk-next-net/master, thanks.
(Updated commit log with the information provided in the mail.)
prev parent reply other threads:[~2017-08-18 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 10:48 [dpdk-stable] " Qi Zhang
2017-08-10 15:15 ` [dpdk-stable] [dpdk-dev] " Kevin Traynor
2017-08-13 0:05 ` Zhang, Qi Z
2017-08-15 17:40 ` Kevin Traynor
2017-08-18 14:35 ` Ferruh Yigit [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=4c8eace2-22ce-f569-30b2-e17825a19cca@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=ktraynor@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
/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).