From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 00/11] Unify the PMD coding style
Date: Sat, 7 Oct 2023 10:33:28 +0800 [thread overview]
Message-ID: <20231007023339.1546659-1-chaoyong.he@corigine.com> (raw)
This patch series aims to unify the coding style of NFP PMD, make the
logics following the same rules, to make it easier to understand and
extend.
Chaoyong He (11):
net/nfp: explicitly compare to null and 0
net/nfp: unify the indent coding style
net/nfp: unify the type of integer variable
net/nfp: standard the local variable coding style
net/nfp: adjust the log statement
net/nfp: standard the comment style
net/nfp: standard the blank character
net/nfp: unify the guide line of header file
net/nfp: rename some parameter and variable
net/nfp: adjust logic to make it more readable
net/nfp: refact the meson build file
drivers/net/nfp/flower/nfp_flower.c | 15 +-
drivers/net/nfp/flower/nfp_flower.h | 34 +-
drivers/net/nfp/flower/nfp_flower_cmsg.c | 18 +-
drivers/net/nfp/flower/nfp_flower_cmsg.h | 62 +-
drivers/net/nfp/flower/nfp_flower_ctrl.c | 36 +-
drivers/net/nfp/flower/nfp_flower_ctrl.h | 6 +-
.../net/nfp/flower/nfp_flower_representor.c | 36 +-
.../net/nfp/flower/nfp_flower_representor.h | 8 +-
drivers/net/nfp/meson.build | 23 +-
drivers/net/nfp/nfd3/nfp_nfd3.h | 39 +-
drivers/net/nfp/nfd3/nfp_nfd3_dp.c | 26 +-
drivers/net/nfp/nfdk/nfp_nfdk.h | 43 +-
drivers/net/nfp/nfdk/nfp_nfdk_dp.c | 12 +-
drivers/net/nfp/nfp_common.c | 763 +++++++++---------
drivers/net/nfp/nfp_common.h | 167 ++--
drivers/net/nfp/nfp_cpp_bridge.c | 135 ++--
drivers/net/nfp/nfp_cpp_bridge.h | 8 +-
drivers/net/nfp/nfp_ctrl.h | 34 +-
drivers/net/nfp/nfp_ethdev.c | 307 ++++---
drivers/net/nfp/nfp_ethdev_vf.c | 191 ++---
drivers/net/nfp/nfp_flow.c | 229 +++---
drivers/net/nfp/nfp_flow.h | 23 +-
drivers/net/nfp/nfp_logs.h | 7 +-
drivers/net/nfp/nfp_rxtx.c | 287 +++----
drivers/net/nfp/nfp_rxtx.h | 36 +-
25 files changed, 1235 insertions(+), 1310 deletions(-)
--
2.39.1
next reply other threads:[~2023-10-07 2:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 2:33 Chaoyong He [this message]
2023-10-07 2:33 ` [PATCH 01/11] net/nfp: explicitly compare to null and 0 Chaoyong He
2023-10-07 2:33 ` [PATCH 02/11] net/nfp: unify the indent coding style Chaoyong He
2023-10-07 2:33 ` [PATCH 03/11] net/nfp: unify the type of integer variable Chaoyong He
2023-10-07 2:33 ` [PATCH 04/11] net/nfp: standard the local variable coding style Chaoyong He
2023-10-07 2:33 ` [PATCH 05/11] net/nfp: adjust the log statement Chaoyong He
2023-10-07 2:33 ` [PATCH 06/11] net/nfp: standard the comment style Chaoyong He
2023-10-07 2:33 ` [PATCH 07/11] net/nfp: standard the blank character Chaoyong He
2023-10-07 2:33 ` [PATCH 08/11] net/nfp: unify the guide line of header file Chaoyong He
2023-10-07 2:33 ` [PATCH 09/11] net/nfp: rename some parameter and variable Chaoyong He
2023-10-07 2:33 ` [PATCH 10/11] net/nfp: adjust logic to make it more readable Chaoyong He
2023-10-07 2:33 ` [PATCH 11/11] net/nfp: refact the meson build file Chaoyong He
2023-10-12 1:26 ` [PATCH v2 00/11] Unify the PMD coding style Chaoyong He
2023-10-12 1:26 ` [PATCH v2 01/11] net/nfp: explicitly compare to null and 0 Chaoyong He
2023-10-12 1:26 ` [PATCH v2 02/11] net/nfp: unify the indent coding style Chaoyong He
2023-10-12 1:26 ` [PATCH v2 03/11] net/nfp: unify the type of integer variable Chaoyong He
2023-10-12 1:26 ` [PATCH v2 04/11] net/nfp: standard the local variable coding style Chaoyong He
2023-10-12 1:26 ` [PATCH v2 05/11] net/nfp: adjust the log statement Chaoyong He
2023-10-12 1:38 ` Stephen Hemminger
2023-10-12 1:40 ` Chaoyong He
2023-10-12 1:26 ` [PATCH v2 06/11] net/nfp: standard the comment style Chaoyong He
2023-10-12 1:27 ` [PATCH v2 07/11] net/nfp: standard the blank character Chaoyong He
2023-10-12 1:27 ` [PATCH v2 08/11] net/nfp: unify the guide line of header file Chaoyong He
2023-10-12 1:27 ` [PATCH v2 09/11] net/nfp: rename some parameter and variable Chaoyong He
2023-10-12 1:27 ` [PATCH v2 10/11] net/nfp: adjust logic to make it more readable Chaoyong He
2023-10-12 1:27 ` [PATCH v2 11/11] net/nfp: refact the meson build file Chaoyong He
2023-10-13 6:06 ` [PATCH v3 00/11] Unify the PMD coding style Chaoyong He
2023-10-13 6:06 ` [PATCH v3 01/11] net/nfp: explicitly compare to null and 0 Chaoyong He
2023-10-13 6:06 ` [PATCH v3 02/11] net/nfp: unify the indent coding style Chaoyong He
2023-10-13 6:06 ` [PATCH v3 03/11] net/nfp: unify the type of integer variable Chaoyong He
2023-10-13 6:06 ` [PATCH v3 04/11] net/nfp: standard the local variable coding style Chaoyong He
2023-10-13 6:06 ` [PATCH v3 05/11] net/nfp: adjust the log statement Chaoyong He
2023-10-13 6:06 ` [PATCH v3 06/11] net/nfp: standard the comment style Chaoyong He
2023-10-13 6:06 ` [PATCH v3 07/11] net/nfp: standard the blank character Chaoyong He
2023-10-13 6:06 ` [PATCH v3 08/11] net/nfp: unify the guide line of header file Chaoyong He
2023-10-13 6:06 ` [PATCH v3 09/11] net/nfp: rename some parameter and variable Chaoyong He
2023-10-13 6:06 ` [PATCH v3 10/11] net/nfp: adjust logic to make it more readable Chaoyong He
2023-10-13 6:06 ` [PATCH v3 11/11] net/nfp: refact the meson build file Chaoyong He
2023-10-16 16:50 ` Ferruh Yigit
2023-10-16 16:50 ` [PATCH v3 00/11] Unify the PMD coding style Ferruh Yigit
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=20231007023339.1546659-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).