From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH 1/3] kni: fix wrong comments
Date: Thu, 22 Apr 2021 11:56:27 +0800 [thread overview]
Message-ID: <1619063789-60922-2-git-send-email-humin29@huawei.com> (raw)
In-Reply-To: <1619063789-60922-1-git-send-email-humin29@huawei.com>
This patch changed 'subsytem' to 'subsystem'.
Fixes: 0c6bc8ef70ba ("kni: memzone pool for alloc and release")
Cc: stable@dpdk.org
Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
---
app/test/test_kni.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test/test_kni.c b/app/test/test_kni.c
index f53a53e..3470005 100644
--- a/app/test/test_kni.c
+++ b/app/test/test_kni.c
@@ -562,7 +562,7 @@ test_kni(void)
}
closedir(dir);
- /* Initialize KNI subsytem */
+ /* Initialize KNI subsystem */
rte_kni_init(KNI_TEST_MAX_PORTS);
if (test_kni_allocate_lcores() < 0) {
--
2.7.4
next prev parent reply other threads:[~2021-04-22 3:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 3:56 [dpdk-dev] [PATCH 0/3] bugfix for kni Min Hu (Connor)
2021-04-22 3:56 ` Min Hu (Connor) [this message]
2021-04-26 13:34 ` [dpdk-dev] [PATCH 1/3] kni: fix wrong comments Ferruh Yigit
2021-04-22 3:56 ` [dpdk-dev] [PATCH 2/3] net/kni: fix rewritten return value Min Hu (Connor)
2021-04-26 13:18 ` Ferruh Yigit
2021-04-27 2:09 ` Min Hu (Connor)
2021-04-27 2:08 ` [dpdk-dev] [PATCH v2] " Min Hu (Connor)
2021-04-29 13:37 ` Ferruh Yigit
2021-04-22 3:56 ` [dpdk-dev] [PATCH 3/3] kni: fix unchecked " Min Hu (Connor)
2021-04-26 13:35 ` Ferruh Yigit
2021-04-26 13:35 ` [dpdk-dev] [PATCH 0/3] bugfix for kni 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=1619063789-60922-2-git-send-email-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).