From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com
Subject: Re: [PATCH 0/8] fix the representor port link status and speed
Date: Fri, 4 Oct 2024 19:17:49 +0100 [thread overview]
Message-ID: <341fd7f4-9cd5-4677-a03e-91cd2c4b54aa@amd.com> (raw)
In-Reply-To: <20240905062511.2710102-1-chaoyong.he@corigine.com>
On 9/5/2024 7:25 AM, Chaoyong He wrote:
> This patch series aims to fix some problems in the representor port link
> status and speed update logic, also do some refactors to the related
> logics.
>
> Qin Ke (8):
> net/nfp: fix incorrect type declaration of some variables
> net/nfp: add help function to check link speed
> net/nfp: add help function to update VF link speed
> net/nfp: rename PF speed update function
> net/nfp: add new data field into representor port structure
> net/nfp: fix representor port link speed update problem
> net/nfp: standardize the use of port index in some functions
> net/nfp: fix representor port link status update problem
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-10-04 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 6:25 Chaoyong He
2024-09-05 6:25 ` [PATCH 1/8] net/nfp: fix incorrect type declaration of some variables Chaoyong He
2024-09-05 6:25 ` [PATCH 2/8] net/nfp: add help function to check link speed Chaoyong He
2024-09-05 6:25 ` [PATCH 3/8] net/nfp: add help function to update VF " Chaoyong He
2024-09-05 6:25 ` [PATCH 4/8] net/nfp: rename PF speed update function Chaoyong He
2024-09-05 6:25 ` [PATCH 5/8] net/nfp: add new data field into representor port structure Chaoyong He
2024-09-05 6:25 ` [PATCH 6/8] net/nfp: fix representor port link speed update problem Chaoyong He
2024-09-05 6:25 ` [PATCH 7/8] net/nfp: standardize the use of port index in some functions Chaoyong He
2024-09-05 6:25 ` [PATCH 8/8] net/nfp: fix representor port link status update problem Chaoyong He
2024-10-04 18:17 ` 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=341fd7f4-9cd5-4677-a03e-91cd2c4b54aa@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=oss-drivers@corigine.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).