From: beilei.xing@intel.com
To: jingjing.wu@intel.com
Cc: dev@dpdk.org, Beilei Xing <beilei.xing@intel.com>
Subject: [PATCH v4 0/2] refine common module
Date: Thu, 6 Apr 2023 07:42:43 +0000 [thread overview]
Message-ID: <20230406074245.82991-1-beilei.xing@intel.com> (raw)
In-Reply-To: <20230404124112.71703-1-beilei.xing@intel.com>
From: Beilei Xing <beilei.xing@intel.com>
Refine common module to support different configuration for
different PMDs.
V4 changes:
- No need to require PTP CAP for CPFL.
V3 changes:
- refine capability get.
Beilei Xing (2):
common/idpf: move PF specific functions from common init
common/idpf: refine capability get
drivers/common/idpf/idpf_common_device.c | 72 ++++-------------
drivers/common/idpf/idpf_common_device.h | 11 +++
drivers/common/idpf/idpf_common_virtchnl.c | 45 +----------
drivers/common/idpf/version.map | 5 ++
drivers/net/cpfl/cpfl_ethdev.c | 91 ++++++++++++++++++++++
drivers/net/idpf/idpf_ethdev.c | 91 ++++++++++++++++++++++
6 files changed, 214 insertions(+), 101 deletions(-)
--
2.26.2
next prev parent reply other threads:[~2023-04-06 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 6:53 [PATCH] common/idpf: move PF specific functions from common init beilei.xing
2023-03-21 7:07 ` [PATCH v2] " beilei.xing
2023-04-04 12:41 ` [PATCH v3 0/2] refine common module beilei.xing
2023-04-04 12:41 ` [PATCH v3 1/2] common/idpf: move PF specific functions from common init beilei.xing
2023-04-04 12:41 ` [PATCH v3 2/2] common/idpf: refine capability get beilei.xing
2023-04-06 7:42 ` beilei.xing [this message]
2023-04-06 7:42 ` [PATCH v4 1/2] common/idpf: move PF specific functions from common init beilei.xing
2023-04-23 8:25 ` Wu, Jingjing
2023-04-06 7:42 ` [PATCH v4 2/2] common/idpf: refine capability get beilei.xing
2023-04-24 8:08 ` [PATCH v5] " beilei.xing
2023-04-26 5:17 ` Wu, Jingjing
2023-04-26 8:11 ` Zhang, Qi Z
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=20230406074245.82991-1-beilei.xing@intel.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.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).