From: Joel Kavanagh <joel.kavanagh@intel.com>
To: Kai Ji <kai.ji@intel.com>, Fan Zhang <fanzhang.oss@gmail.com>
Cc: dev@dpdk.org, stable@dpdk.org, Joel Kavanagh <joel.kavanagh@intel.com>
Subject: [PATCH v2 3/4] crypto/qat: fix typo in log message
Date: Wed, 17 Jul 2024 15:49:07 +0000 [thread overview]
Message-ID: <20240717154908.2281023-4-joel.kavanagh@intel.com> (raw)
In-Reply-To: <20240717154908.2281023-1-joel.kavanagh@intel.com>
This patch fixes a typo in the log message for rte_security support.
The typo incorrectly spelled 'enabled' as 'ensabled' in the
log message indicating that rte_security support is enabled.
Fixes: fb3b9f492205 ("crypto/qat: rework burst data path")
Cc: stable@dpdk.org
Signed-off-by: Joel Kavanagh <joel.kavanagh@intel.com>
---
drivers/crypto/qat/qat_sym.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
index b41d1b1def..d979ae6489 100644
--- a/drivers/crypto/qat/qat_sym.c
+++ b/drivers/crypto/qat/qat_sym.c
@@ -291,7 +291,7 @@ qat_sym_dev_create(struct qat_pci_device *qat_pci_dev)
}
cryptodev->feature_flags |= RTE_CRYPTODEV_FF_SECURITY;
- QAT_LOG(INFO, "Device %s rte_security support ensabled", name);
+ QAT_LOG(INFO, "Device %s rte_security support enabled", name);
} else {
QAT_LOG(INFO, "Device %s rte_security support disabled", name);
}
--
2.34.1
next prev parent reply other threads:[~2024-07-18 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 13:14 [PATCH v1] crypto/aesni_mb: fix typo in error message Joel Kavanagh
2024-07-12 14:32 ` Dooley, Brian
2024-07-17 15:49 ` [PATCH v2 0/4] Fix spelling mistakes Joel Kavanagh
2024-07-17 15:49 ` [PATCH v2 1/4] crypto/aesni_mb: fix typo in error message Joel Kavanagh
2024-07-18 15:42 ` [EXTERNAL] " Akhil Goyal
2024-07-17 15:49 ` [PATCH v2 2/4] app/test: fix typo in error message allocation Joel Kavanagh
2024-07-17 15:49 ` Joel Kavanagh [this message]
2024-07-17 15:49 ` [PATCH v2 4/4] doc: fix typo in l2fwd-crypto guide Joel Kavanagh
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=20240717154908.2281023-4-joel.kavanagh@intel.com \
--to=joel.kavanagh@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=kai.ji@intel.com \
--cc=stable@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).