From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Jin Liu <jin.liu@corigine.com>,
stable@dpdk.org
Subject: Re: [PATCH] net/nfp: only flush specified port flow table
Date: Thu, 16 Feb 2023 17:08:50 +0000 [thread overview]
Message-ID: <7c9dcbf2-ce8c-b7ad-ba69-0cd4e630d32a@amd.com> (raw)
In-Reply-To: <20230216063644.13109-1-chaoyong.he@corigine.com>
On 2/16/2023 6:36 AM, Chaoyong He wrote:
> From: Jin Liu <jin.liu@corigine.com>
>
> The flow flush function will destroy all the flow table on all the
> port of NFP nic rather than the provide port. Modify logic, only
> destroy the flow table on the corresponding port.
>
> Fixes: 30ecce522732 ("net/nfp: support flow API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jin Liu <jin.liu@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-02-16 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 6:36 Chaoyong He
2023-02-16 17:08 ` 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=7c9dcbf2-ce8c-b7ad-ba69-0cd4e630d32a@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=jin.liu@corigine.com \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).