automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: wenxuanx.wu@intel.com
Subject: |WARNING| pw110277 [PATCH v5 1/4] lib/ethdev: introduce protocol type based buffer split
Date: Tue, 26 Apr 2022 13:37:18 +0200 (CEST)	[thread overview]
Message-ID: <20220426113718.A254A120DB4@dpdk.org> (raw)
In-Reply-To: <20220426111338.1074785-2-wenxuanx.wu@intel.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#70: 
Protocol based buffer split consists of splitting a received packet into two

WARNING:TYPO_SPELLING: 'splitted' may be misspelled - perhaps 'split'?
#95: 
consists of MAC_IP_UDP_PAYLOAD will be splitted like following:

WARNING:LONG_LINE_COMMENT: line length of 103 exceeds 100 columns
#150: FILE: lib/ethdev/rte_ethdev.c:1713:
+			/* Length and protocol are exclusive here, so make sure length is 0 in protocol

WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#151: FILE: lib/ethdev/rte_ethdev.c:1714:
+			/* Length and protocol are exclusive here, so make sure length is 0 in protocol
+			based buffer split. */

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#151: FILE: lib/ethdev/rte_ethdev.c:1714:
+			based buffer split. */

total: 0 errors, 5 warnings, 86 lines checked

           reply	other threads:[~2022-04-26 11:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220426111338.1074785-2-wenxuanx.wu@intel.com>]

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=20220426113718.A254A120DB4@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=wenxuanx.wu@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).