From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, kai.ji@intel.com
Subject: [PATCH v7 5/5] ipsec: fix usage of RTE_LOGTYPE_USER1
Date: Tue, 21 Feb 2023 10:55:53 -0800 [thread overview]
Message-ID: <20230221185553.513432-6-stephen@networkplumber.org> (raw)
In-Reply-To: <20230221185553.513432-1-stephen@networkplumber.org>
There already is a logtype in this driver, use it!
Fixes: b35848bc01f6 ("crypto/ipsec_mb: add multi-process IPC request handler")
Cc: kai.ji@intel.com
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
drivers/crypto/ipsec_mb/ipsec_mb_ops.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/crypto/ipsec_mb/ipsec_mb_ops.c b/drivers/crypto/ipsec_mb/ipsec_mb_ops.c
index 3e52f9567401..e9eb0d15b794 100644
--- a/drivers/crypto/ipsec_mb/ipsec_mb_ops.c
+++ b/drivers/crypto/ipsec_mb/ipsec_mb_ops.c
@@ -7,6 +7,7 @@
#include <rte_common.h>
#include <rte_malloc.h>
+#include <rte_log.h>
#include "ipsec_mb_private.h"
@@ -125,7 +126,7 @@ ipsec_mb_secondary_qp_op(int dev_id, int qp_id,
qp_req_msg.num_fds = 0;
ret = rte_mp_request_sync(&qp_req_msg, &qp_resp, &ts);
if (ret) {
- RTE_LOG(ERR, USER1, "Create MR request to primary process failed.");
+ IPSEC_MB_LOG(ERR, "Create MR request to primary process failed.");
return -1;
}
qp_resp_msg = &qp_resp.msgs[0];
--
2.39.1
prev 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 ` [PATCH v7 0/5] Convert us of RTE_LOGTYPE_USER1 in libraries Stephen Hemminger
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 ` Stephen Hemminger [this message]
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-6-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=kai.ji@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).