From: Kevin Traynor <ktraynor@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, asomalap@amd.com, dev@dpdk.org
Cc: stable@dpdk.org, Ravi Kumar <ravi1.kumar@amd.com>,
Thomas Monjalon <thomas@monjalon.net>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-stable] [PATCH v2] net/axgbe: support flow control API
Date: Fri, 31 Jan 2020 17:50:15 +0000 [thread overview]
Message-ID: <2ecea1af-ab60-24f2-3306-da1fa987fa50@redhat.com> (raw)
In-Reply-To: <088b7dd5-0171-ff4a-911f-adb6badffea3@intel.com>
On 31/01/2020 13:47, Ferruh Yigit wrote:
> On 1/30/2020 6:35 AM, asomalap@amd.com wrote:
>> From: Amaranath Somalapuram <asomalap@amd.com>
>>
>> adding api for flow_ctrl_get and flow_ctrl_set
>> by default axgbe driver flow control is dissabled
>> adding dpdk flow control to set water high and low
s/dissabled/disabled/
Also, please add some punctuation to the commit message.
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Amaranath Somalapuram <asomalap@amd.com>
>
> Please cc the maintainer.
>
> This is a new feature and it received late in the release cycle, I am OK to get
> it for -rc2 if it is acked by maintainer on time (same for priority flow
> control) but if not it will be postponed to next release.
>
> And related to the back-porting request, "Cc: stable@dpdk.org", this is a new
> feature in the PMD and backporting it is the discretion of the LTS maintainers,
> cc'ed them for comment.
>
Which LTS is it requested for/tested on?
> Thanks,
> ferruh
>
next prev parent reply other threads:[~2020-01-31 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 6:35 asomalap
2020-01-31 13:47 ` Ferruh Yigit
2020-01-31 17:50 ` Kevin Traynor [this message]
2020-02-03 4:40 ` Somalapuram, Amaranath
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=2ecea1af-ab60-24f2-3306-da1fa987fa50@redhat.com \
--to=ktraynor@redhat.com \
--cc=asomalap@amd.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ravi1.kumar@amd.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).