From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 0/3] NFP PMD enhancement
Date: Wed, 30 Oct 2024 16:19:07 +0800 [thread overview]
Message-ID: <20241030081910.209308-1-chaoyong.he@corigine.com> (raw)
This patch series fix one problem imported by mistake and add support of
two new APIs.
Chaoyong He (3):
net/nfp: extract function to check physical reprsentor
net/nfp: add support for EEPROM functions
net/nfp: add support for port identify
.../net/nfp/flower/nfp_flower_representor.c | 124 +++++++-
.../net/nfp/flower/nfp_flower_representor.h | 1 +
drivers/net/nfp/nfp_ethdev.c | 7 +
drivers/net/nfp/nfp_net_common.c | 288 ++++++++++++++++++
drivers/net/nfp/nfp_net_common.h | 8 +
drivers/net/nfp/nfpcore/nfp_nsp.c | 96 ++++++
drivers/net/nfp/nfpcore/nfp_nsp.h | 10 +
drivers/net/nfp/nfpcore/nfp_nsp_eth.c | 36 +++
8 files changed, 564 insertions(+), 6 deletions(-)
--
2.43.5
next reply other threads:[~2024-10-30 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 8:19 Chaoyong He [this message]
2024-10-30 8:19 ` [PATCH 1/3] net/nfp: extract function to check physical reprsentor Chaoyong He
2024-10-30 8:19 ` [PATCH 2/3] net/nfp: add support for EEPROM functions Chaoyong He
2024-10-30 8:19 ` [PATCH 3/3] net/nfp: add support for port identify Chaoyong He
2024-10-30 8:27 ` [PATCH 0/4] NFP PMD enhancement Chaoyong He
2024-10-30 8:27 ` [PATCH 1/4] net/nfp: fix port index problem Chaoyong He
2024-10-30 8:27 ` [PATCH 2/4] net/nfp: extract function to check physical reprsentor Chaoyong He
2024-10-30 8:27 ` [PATCH 3/4] net/nfp: add support for EEPROM functions Chaoyong He
2024-10-30 8:27 ` [PATCH 4/4] net/nfp: add support for port identify Chaoyong He
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=20241030081910.209308-1-chaoyong.he@corigine.com \
--to=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).