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/9] support multiple PF flower firmware
Date: Tue, 29 Oct 2024 23:34:16 +0000 [thread overview]
Message-ID: <77276e55-d6a5-4b39-a580-3422acfa1298@amd.com> (raw)
In-Reply-To: <20241021063301.4146214-1-chaoyong.he@corigine.com>
On 10/21/2024 7:32 AM, Chaoyong He wrote:
> This patch series add support of the multiple PF flower firmware.
>
> Peng Zhang (9):
> net/nfp: extract the function to allocate the PHY
> net/nfp: extract the function to initialize the PF
> net/nfp: extract the function to allocate PF
> net/nfp: extract the function to allocate the VF
> net/nfp: revise the number of PF representor port
> net/nfp: initialize the representor port of the multiple PF
> net/nfp: ignore useless message for multiple PF
> net/nfp: add the new operations for multiple PF
> net/nfp: update the Tx and Rx function for multiple PF
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-10-29 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 6:32 Chaoyong He
2024-10-21 6:32 ` [PATCH 1/9] net/nfp: extract the function to allocate the PHY Chaoyong He
2024-10-21 6:32 ` [PATCH 2/9] net/nfp: extract the function to initialize the PF Chaoyong He
2024-10-21 6:32 ` [PATCH 3/9] net/nfp: extract the function to allocate PF Chaoyong He
2024-10-21 6:32 ` [PATCH 4/9] net/nfp: extract the function to allocate the VF Chaoyong He
2024-10-21 6:32 ` [PATCH 5/9] net/nfp: revise the number of PF representor port Chaoyong He
2024-10-21 6:32 ` [PATCH 6/9] net/nfp: initialize the representor port of the multiple PF Chaoyong He
2024-10-21 6:32 ` [PATCH 7/9] net/nfp: ignore useless message for " Chaoyong He
2024-10-21 6:33 ` [PATCH 8/9] net/nfp: add the new operations " Chaoyong He
2024-10-21 6:33 ` [PATCH 9/9] net/nfp: update the Tx and Rx function " Chaoyong He
2024-10-29 23:34 ` 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=77276e55-d6a5-4b39-a580-3422acfa1298@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).