automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nandini Persad <nandinipersad361@gmail.com>
Subject: |WARNING| pw143916 [PATCH v3] doc: add new driver guidelines
Date: Tue, 10 Sep 2024 16:59:01 +0200 (CEST)	[thread overview]
Message-ID: <20240910145901.1163B121D10@dpdk.org> (raw)
In-Reply-To: <20240910145801.46186-1-nandinipersad361@gmail.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143916

_coding style issues_


WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#88: 
Co-authored-by: Ferruh Yigit <ferruh.yigit@amd.com>

WARNING:BAD_SIGN_OFF: Non-standard signature: Co-authored-by:
#89: 
Co-authored-by: Thomas Mojalon <thomas@monjalon.net>

WARNING:TYPO_SPELLING: 'Upsreaming' may be misspelled - perhaps 'Upstreaming'?
#107: FILE: doc/guides/contributing/new_driver.rst:5:
+Upsreaming New DPDK Drivers Guide

WARNING:TYPO_SPELLING: 'continously' may be misspelled - perhaps 'continuously'?
#110: FILE: doc/guides/contributing/new_driver.rst:8:
+The DPDK project continously grows its ecosystem by adding support for new

ERROR:TRAILING_WHITESPACE: trailing whitespace
#111: FILE: doc/guides/contributing/new_driver.rst:9:
+devices. This document is designed to assist contributors in creating DPDK $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#115: FILE: doc/guides/contributing/new_driver.rst:13:
+systems and guarantees community maintenance in future releases. $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#131: FILE: doc/guides/contributing/new_driver.rst:29:
+the release cycle, or even during the prior release, is advisable. $

WARNING:TYPO_SPELLING: 'undertand' may be misspelled - perhaps 'understand'?
#176: FILE: doc/guides/contributing/new_driver.rst:74:
+it is enabled for and helps users to undertand the reasoning and intention

WARNING:TYPO_SPELLING: 'funtionality' may be misspelled - perhaps 'functionality'?
#190: FILE: doc/guides/contributing/new_driver.rst:88:
+and should maintain funtionality.

ERROR:TRAILING_WHITESPACE: trailing whitespace
#241: FILE: doc/guides/contributing/new_driver.rst:139:
+* TSO / LRO $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#242: FILE: doc/guides/contributing/new_driver.rst:140:
+* Rx / Tx Descriptor Status $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#244: FILE: doc/guides/contributing/new_driver.rst:142:
+* Flow Offload $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#250: FILE: doc/guides/contributing/new_driver.rst:148:
+* FEC $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#252: FILE: doc/guides/contributing/new_driver.rst:150:
+* Register Dump $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#253: FILE: doc/guides/contributing/new_driver.rst:151:
+* Time Synchronization, PTP $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#299: FILE: doc/guides/contributing/new_driver.rst:197:
+For more information on contributing to DPDK, $

total: 10 errors, 6 warnings, 200 lines checked

  parent reply	other threads:[~2024-09-10 14:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240910145801.46186-1-nandinipersad361@gmail.com>
2024-09-10 14:31 ` |SUCCESS| " qemudev
2024-09-10 14:35 ` qemudev
2024-09-10 14:59 ` checkpatch [this message]
2024-09-10 16:04 ` |FAILURE| " 0-day Robot
2024-09-10 21:12 ` |SUCCESS| pw143916 [PATCH] [v3] " dpdklab
2024-09-10 21:18 ` dpdklab
2024-09-10 21:22 ` dpdklab
2024-09-10 21:23 ` dpdklab
2024-09-10 21:26 ` |PENDING| " dpdklab
2024-09-10 21:28 ` |SUCCESS| " dpdklab
2024-09-10 21:36 ` dpdklab
2024-09-10 21:41 ` dpdklab
2024-09-10 22:00 ` dpdklab
2024-09-10 22:06 ` dpdklab
2024-09-10 22:14 ` dpdklab
2024-09-10 22:15 ` dpdklab
2024-09-10 22:15 ` dpdklab
2024-09-10 22:18 ` dpdklab
2024-09-10 22:48 ` dpdklab
2024-09-11  0:25 ` dpdklab
2024-09-11  0:26 ` dpdklab
2024-09-16  1:40 ` dpdklab
2024-09-16  7:11 ` dpdklab

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=20240910145901.1163B121D10@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=nandinipersad361@gmail.com \
    --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).