DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
	Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 0/8] make the logic conform the coding style of DPDK
Date: Fri, 19 May 2023 10:59:42 +0800	[thread overview]
Message-ID: <20230519025950.1642943-1-chaoyong.he@corigine.com> (raw)

Modify some logic of nfp PMD, to make it conform the coding style
of DPDK.

Also remove some unnecessary macro and functions which DPDK has
already provided.

Chaoyong He (8):
  net/nfp: reuse the ring buffer struct
  net/nfp: modify the rxq struct
  net/nfp: modify the Rx descriptor struct
  net/nfp: modify the txq struct
  net/nfp: remove the custom round macro
  net/nfp: remove the unneeded comment
  net/nfp: revise cast from void pointer
  net/nfp: revise the logic of MAC address

 drivers/net/nfp/flower/nfp_flower.c           |  42 ++--
 drivers/net/nfp/flower/nfp_flower_ctrl.c      |   8 +-
 .../net/nfp/flower/nfp_flower_representor.c   |  39 ++--
 drivers/net/nfp/nfd3/nfp_nfd3_dp.c            |   7 +-
 drivers/net/nfp/nfdk/nfp_nfdk_dp.c            |  16 +-
 drivers/net/nfp/nfp_common.c                  |  38 +---
 drivers/net/nfp/nfp_common.h                  |  18 +-
 drivers/net/nfp/nfp_cpp_bridge.c              |  14 --
 drivers/net/nfp/nfp_cpp_bridge.h              |  14 --
 drivers/net/nfp/nfp_ctrl.h                    |  11 --
 drivers/net/nfp/nfp_ethdev.c                  |  33 +---
 drivers/net/nfp/nfp_ethdev_vf.c               |  34 +---
 drivers/net/nfp/nfp_flow.c                    |  60 +++---
 drivers/net/nfp/nfp_rxtx.c                    |  44 ++---
 drivers/net/nfp/nfp_rxtx.h                    | 187 ++++++++----------
 drivers/net/nfp/nfpcore/nfp_cpp_pcie_ops.c    |   2 +-
 drivers/net/nfp/nfpcore/nfp_nsp.h             |   4 +-
 drivers/net/nfp/nfpcore/nfp_nsp_eth.c         |   8 +-
 drivers/net/nfp/nfpcore/nfp_rtsym.c           |   4 +-
 drivers/net/nfp/nfpcore/nfp_rtsym.h           |  19 --
 20 files changed, 200 insertions(+), 402 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-05-19  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19  2:59 Chaoyong He [this message]
2023-05-19  2:59 ` [PATCH 1/8] net/nfp: reuse the ring buffer struct Chaoyong He
2023-05-19  2:59 ` [PATCH 2/8] net/nfp: modify the rxq struct Chaoyong He
2023-05-19  2:59 ` [PATCH 3/8] net/nfp: modify the Rx descriptor struct Chaoyong He
2023-05-19  2:59 ` [PATCH 4/8] net/nfp: modify the txq struct Chaoyong He
2023-05-19  2:59 ` [PATCH 5/8] net/nfp: remove the custom round macro Chaoyong He
2023-05-19  2:59 ` [PATCH 6/8] net/nfp: remove the unneeded comment Chaoyong He
2023-05-19  2:59 ` [PATCH 7/8] net/nfp: revise cast from void pointer Chaoyong He
2023-05-19  2:59 ` [PATCH 8/8] net/nfp: revise the logic of MAC address Chaoyong He
2023-05-19 13:55 ` [PATCH 0/8] make the logic conform the coding style of DPDK 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=20230519025950.1642943-1-chaoyong.he@corigine.com \
    --to=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=niklas.soderlund@corigine.com \
    --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).