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/3] refactor the nfp log subsystem
Date: Fri, 17 Feb 2023 10:45:36 +0800 [thread overview]
Message-ID: <20230217024539.16514-1-chaoyong.he@corigine.com> (raw)
Follow the advice from community reviewer, we get rid of the use of
RTE log level type and RTE_LOG_*() macro, and also wrap the rte_log()
with our own log macro.
Chaoyong He (3):
net/nfp: add the log source file
net/nfp: get rid of the usage of RTE log level type
net/nfp: get rid of the usage of RTE log macro
drivers/net/nfp/flower/nfp_flower.c | 10 ++---
drivers/net/nfp/flower/nfp_flower_ctrl.c | 2 +-
drivers/net/nfp/meson.build | 1 +
drivers/net/nfp/nfp_common.c | 3 --
drivers/net/nfp/nfp_cpp_bridge.c | 48 ++++++++++------------
drivers/net/nfp/nfp_ethdev.c | 4 +-
drivers/net/nfp/nfp_ethdev_vf.c | 4 +-
drivers/net/nfp/nfp_logs.c | 20 +++++++++
drivers/net/nfp/nfp_logs.h | 8 +++-
drivers/net/nfp/nfp_rxtx.c | 10 ++---
drivers/net/nfp/nfpcore/nfp_cpp_pcie_ops.c | 1 +
11 files changed, 65 insertions(+), 46 deletions(-)
create mode 100644 drivers/net/nfp/nfp_logs.c
--
2.29.3
next reply other threads:[~2023-02-17 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 2:45 Chaoyong He [this message]
2023-02-17 2:45 ` [PATCH 1/3] net/nfp: add the log source file Chaoyong He
2023-02-17 2:45 ` [PATCH 2/3] net/nfp: get rid of the usage of RTE log level type Chaoyong He
2023-02-17 13:59 ` Ferruh Yigit
2023-02-20 1:36 ` Chaoyong He
2023-02-20 10:09 ` Ferruh Yigit
2023-02-20 16:16 ` Stephen Hemminger
2023-02-20 16:32 ` Ferruh Yigit
2023-02-17 2:45 ` [PATCH 3/3] net/nfp: get rid of the usage of RTE log macro Chaoyong He
2023-02-20 12:03 ` [PATCH 0/3] refactor the nfp log subsystem 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=20230217024539.16514-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).