From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: |WARNING| pw109274 [RFC PATCH v1 08/24] dts: merge DTS doc/dts_gsg/image/virt_flow.svg to DPDK
Date: Wed, 6 Apr 2022 17:13:07 +0200 (CEST) [thread overview]
Message-ID: <20220406151307.AA70D122BA2@dpdk.org> (raw)
In-Reply-To: <20220406151106.2915304-9-juraj.linkes@pantheon.tech>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/109274
_coding style issues_
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
WARNING:TYPO_SPELLING: 'Virutal' may be misspelled - perhaps 'Virtual'?
#135: FILE: dts/doc/dts_gsg/image/virt_flow.svg:70:
+ <desc>scene:Virutal Scenario</desc>
WARNING:TYPO_SPELLING: 'Virutal' may be misspelled - perhaps 'Virtual'?
#155: FILE: dts/doc/dts_gsg/image/virt_flow.svg:90:
+ <text x="24.84" y="1165.8" class="st3" v:langID="1033"><v:paragraph v:horizAlign="1"/><v:tabList/>scene:Virutal <tspan
WARNING:TYPO_SPELLING: 'Virutal' may be misspelled - perhaps 'Virtual'?
#224: FILE: dts/doc/dts_gsg/image/virt_flow.svg:159:
+ <desc>vm_dut:Virutal DUT</desc>
WARNING:TYPO_SPELLING: 'Virutal' may be misspelled - perhaps 'Virtual'?
#244: FILE: dts/doc/dts_gsg/image/virt_flow.svg:179:
+ <text x="4.9" y="1174.2" class="st3" v:langID="1033"><v:paragraph v:horizAlign="1"/><v:tabList/>vm_dut:Virutal DUT</text> </g>
WARNING:TYPO_SPELLING: 'Destory' may be misspelled - perhaps 'Destroy'?
#752: FILE: dts/doc/dts_gsg/image/virt_flow.svg:687:
+ <desc>Destory_vfs(pf_device)</desc>
WARNING:TYPO_SPELLING: 'Destory' may be misspelled - perhaps 'Destroy'?
#756: FILE: dts/doc/dts_gsg/image/virt_flow.svg:691:
+ <text x="17.09" y="1183.2" class="st10" v:langID="1033"><v:paragraph v:horizAlign="1"/><v:tabList/>Destory_vfs(pf_device)</text> </g>
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 7 warnings, 717 lines checked
parent reply other threads:[~2022-04-06 15:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220406151106.2915304-9-juraj.linkes@pantheon.tech>]
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=20220406151307.AA70D122BA2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--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).