From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dean Marx <dmarx@iol.unh.edu>
Subject: |WARNING| pw153798 [PATCH v1 1/3] dts: rewrite README
Date: Tue, 27 May 2025 17:37:57 +0200 (CEST) [thread overview]
Message-ID: <20250527153757.743E4125267@dpdk.org> (raw)
In-Reply-To: <20250527153734.368235-1-dmarx@iol.unh.edu>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153798
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#84:
Remove unnecessary information from README.md, and add new sections to clarify
ERROR:TRAILING_WHITESPACE: trailing whitespace
#103: FILE: dts/README.md:3:
+DTS is a testing framework and set of testsuites for end to end testing of DPDK and DPDK $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#104: FILE: dts/README.md:4:
+enabled hardware. Unlike the DPDK unit test application, DTS is intended to be used to $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#106: FILE: dts/README.md:6:
+a traffic generator node which will send packets to a system under test node which is $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#126: FILE: dts/README.md:11:
+DTS is a python application which will control a traffic generator node (TG) and system $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#127: FILE: dts/README.md:12:
+under test node (SUT). The nodes represent a DPDK device (usually a NIC) located on a $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#135: FILE: dts/README.md:19:
+TG node connected to a dual interface NIC which is the SUT node. Interface 0 on TG <-> interface 0 $
total: 6 errors, 1 warnings, 120 lines checked
prev parent reply other threads:[~2025-05-27 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250527153734.368235-1-dmarx@iol.unh.edu>
2025-05-27 15:11 ` |WARNING| pw153798-153797 " qemudev
2025-05-27 15:37 ` checkpatch [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=20250527153757.743E4125267@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=test-report@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).