|WARNING| pw114370 [PATCH V6 17/17] examples/pipeline: call the code generation and build CLI commands

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| pw114370 [PATCH V6 17/17] examples/pipeline: call the code generation and build CLI commands
Date: Thu, 28 Jul 2022 17:15:05 +0200 (CEST)	[thread overview]
Message-ID: <20220728151506.0DA33120765@dpdk.org> (raw)
In-Reply-To: <20220728151147.603265-18-cristian.dumitrescu@intel.com>

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

_coding style issues_


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

total: 0 errors, 15 warnings, 876 lines checked

next      parent reply	other threads:[~2022-07-28 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220728151147.603265-18-cristian.dumitrescu@intel.com>
2022-07-28 15:15 ` checkpatch [this message]
2022-07-28 16:28 ` |SUCCESS| " 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=20220728151506.0DA33120765@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).