automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: |WARNING| pw121853 [PATCH 11/11] examples/pipeline: add IPsec example
Date: Wed, 11 Jan 2023 21:57:58 +0100 (CET)	[thread overview]
Message-ID: <20230111205758.318EF1234F4@dpdk.org> (raw)
In-Reply-To: <20230111205608.87953-12-cristian.dumitrescu@intel.com>

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

_coding style issues_


WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#90: FILE: examples/pipeline/examples/ipsec.cli:5:
+#	./build/examples/dpdk-pipeline -l0-1 --vdev crypto_aesni_mb0 -- -s ./examples/pipeline/examples/ipsec.cli

ERROR:TRAILING_WHITESPACE: trailing whitespace
#230: FILE: examples/pipeline/examples/ipsec.spec:53:
+^Ibit<16> dst_port^I$

total: 1 errors, 1 warnings, 434 lines checked

  parent reply	other threads:[~2023-01-11 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230111205608.87953-12-cristian.dumitrescu@intel.com>
2023-01-11 20:55 ` |FAILURE| pw121843-121853 " qemudev
2023-01-11 20:57 ` checkpatch [this message]
2023-01-11 21:39 ` |FAILURE| pw121853 " 0-day Robot

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=20230111205758.318EF1234F4@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=cristian.dumitrescu@intel.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).