automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-test-report] |WARNING| pw65307 [RFC] meter: fix ABI break due to experimental tag removal
Date: Wed, 29 Jan 2020 13:30:17 +0100 (CET)	[thread overview]
Message-ID: <20200129123017.62B151BFD1@dpdk.org> (raw)
In-Reply-To: <20200129122953.2016199-1-ferruh.yigit@intel.com>

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

_coding style issues_


WARNING:LONG_LINE: line over 90 characters
#121: FILE: lib/librte_eal/common/include/rte_function_versioning.h:50:
+#define VERSION_SYMBOL_EXPERIMENTAL(b, e) __asm__(".symver " RTE_STR(b) RTE_STR(e) ", " RTE_STR(b) "@EXPERIMENTAL")

WARNING:LONG_LINE: line over 90 characters
#173: FILE: lib/librte_meter/rte_meter.c:160:
+MAP_STATIC_SYMBOL(int rte_meter_trtcm_rfc4115_profile_config(struct rte_meter_trtcm_rfc4115_profile *p,

WARNING:LONG_LINE: line over 90 characters
#174: FILE: lib/librte_meter/rte_meter.c:161:
+		struct rte_meter_trtcm_rfc4115_params *params), rte_meter_trtcm_rfc4115_profile_config_s);

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#176: FILE: lib/librte_meter/rte_meter.c:163:
+int

WARNING:LONG_LINE: line over 90 characters
#210: FILE: lib/librte_meter/rte_meter.c:204:
+		 struct rte_meter_trtcm_rfc4115_profile *p), rte_meter_trtcm_rfc4115_config_s);

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#212: FILE: lib/librte_meter/rte_meter.c:206:
+int

total: 0 errors, 6 warnings, 125 lines checked

           reply	other threads:[~2020-01-29 12:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200129122953.2016199-1-ferruh.yigit@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=20200129123017.62B151BFD1@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=ferruh.yigit@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).