From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: ke1.xu@intel.com, weiyuanx.li@intel.com, lijuan.tu@intel.com,
qi.fu@intel.com
Subject: [DTS][PATCH V1 1/4] tests/vf_offload: fix a typo.
Date: Fri, 9 Dec 2022 17:38:18 +0800 [thread overview]
Message-ID: <20221209093821.341263-2-ke1.xu@intel.com> (raw)
In-Reply-To: <20221209093821.341263-1-ke1.xu@intel.com>
Checksum is wrongly spelled as checksup.
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
tests/TestSuite_vf_offload.py | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tests/TestSuite_vf_offload.py b/tests/TestSuite_vf_offload.py
index 75c75f05..c7f618e3 100644
--- a/tests/TestSuite_vf_offload.py
+++ b/tests/TestSuite_vf_offload.py
@@ -265,7 +265,7 @@ class TestVfOffload(TestCase):
(
ip_checksum,
tcp_checksum,
- udp_checksup,
+ udp_checksum,
sctp_checksum,
) = packet_received.split(";")
print(
@@ -273,8 +273,8 @@ class TestVfOffload(TestCase):
ip_checksum,
"tcp_checksum:, ",
tcp_checksum,
- "udp_checksup: ",
- udp_checksup,
+ "udp_checksum: ",
+ udp_checksum,
"sctp_checksum: ",
sctp_checksum,
)
@@ -284,9 +284,9 @@ class TestVfOffload(TestCase):
if tcp_checksum != "??":
packet_type = "TCP"
l4_checksum = tcp_checksum
- elif udp_checksup != "??":
+ elif udp_checksum != "??":
packet_type = "UDP"
- l4_checksum = udp_checksup
+ l4_checksum = udp_checksum
elif sctp_checksum != "??":
packet_type = "SCTP"
l4_checksum = sctp_checksum
--
2.25.1
next prev parent reply other threads:[~2022-12-09 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 9:38 [DTS][PATCH V1 0/4] add vf checksum offload and tso case for tunnel packets Ke Xu
2022-12-09 9:38 ` Ke Xu [this message]
2022-12-09 9:38 ` [DTS][PATCH V1 2/4] tests/vf_offload: add vf checksum hw offload case for tunneling packets Ke Xu
2022-12-09 9:38 ` [DTS][PATCH V1 3/4] tests/vf_offload: add vf tso " Ke Xu
2022-12-09 9:38 ` [DTS][PATCH V1 4/4] tests/vf_offload: dts adaptation DPDK checksum function changes Ke Xu
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=20221209093821.341263-2-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=qi.fu@intel.com \
--cc=weiyuanx.li@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).