From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v7 0/5] Convert us of RTE_LOGTYPE_USER1 in libraries
Date: Tue, 21 Feb 2023 10:55:48 -0800 [thread overview]
Message-ID: <20230221185553.513432-1-stephen@networkplumber.org> (raw)
In-Reply-To: <0230208044825.1682620-1-stephen@networkplumber.org>
The DPDK libraries and drivers should not be using the USER1 logtype.
v7 - fix review comments. Replace USER1 in ip_frag and vhost crypto.
Stephen Hemminger (5):
ip_frag: use a dynamic logtype
reorder: use a dynamic logtype
latencystats: use dynamic logtype
vhost: use logtype instead of RTE_LOGTYPE_USER1
ipsec: fix usage of RTE_LOGTYPE_USER1
drivers/crypto/ipsec_mb/ipsec_mb_ops.c | 3 ++-
lib/ip_frag/ip_frag_common.h | 5 ++++-
lib/ip_frag/rte_ip_frag_common.c | 8 +++++---
lib/latencystats/rte_latencystats.c | 3 ++-
lib/reorder/rte_reorder.c | 6 +++---
lib/vhost/fd_man.c | 4 ++--
lib/vhost/vhost_crypto.c | 22 +++++++++++-----------
7 files changed, 29 insertions(+), 22 deletions(-)
--
2.39.1
next parent reply other threads:[~2023-02-21 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0230208044825.1682620-1-stephen@networkplumber.org>
2023-02-21 18:55 ` Stephen Hemminger [this message]
2023-02-21 18:55 ` [PATCH v7 1/5] ip_frag: use a dynamic logtype Stephen Hemminger
2023-02-21 18:55 ` [PATCH v7 2/5] reorder: " Stephen Hemminger
2023-02-21 18:55 ` [PATCH v7 3/5] latencystats: use " Stephen Hemminger
2023-02-21 18:55 ` [PATCH v7 4/5] vhost: use logtype instead of RTE_LOGTYPE_USER1 Stephen Hemminger
2023-02-21 18:55 ` [PATCH v7 5/5] ipsec: fix usage " Stephen Hemminger
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=20230221185553.513432-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).