From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw87924 [PATCH 3/5] pipeline: support non-incremental table updates
Date: Tue, 16 Feb 2021 10:38:47 +0100 (CET) [thread overview]
Message-ID: <20210216093847.C2786C906@dpdk.org> (raw)
In-Reply-To: <20210215162151.5655-3-cristian.dumitrescu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/87924
_coding style issues_
WARNING:TYPO_SPELLING: 'peding' may be misspelled - perhaps 'pending'?
#76: FILE: lib/librte_pipeline/rte_swx_ctl.c:607:
+table_is_update_pending(struct table *table, int consider_peding_default)
WARNING:TYPO_SPELLING: 'peding' may be misspelled - perhaps 'pending'?
#94: FILE: lib/librte_pipeline/rte_swx_ctl.c:625:
+ if (consider_peding_default && table->pending_default)
WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#245: FILE: lib/librte_pipeline/rte_swx_ctl.c:1231:
+ return 0;
+ } else {
WARNING:LONG_LINE: line length of 103 exceeds 100 columns
#257: FILE: lib/librte_pipeline/rte_swx_ctl.c:1243:
+ status = table_entry_list_duplicate(ctl, table_id, &list, &table->pending_add);
WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#261: FILE: lib/librte_pipeline/rte_swx_ctl.c:1247:
+ status = table_entry_list_duplicate(ctl, table_id, &list, &table->pending_modify1);
WARNING:LONG_LINE: line length of 114 exceeds 100 columns
#266: FILE: lib/librte_pipeline/rte_swx_ctl.c:1252:
+ ts_next->obj = table->ops.create(&table->params, &list, table->info.args, ctl->numa_node);
total: 0 errors, 6 warnings, 328 lines checked
parent reply other threads:[~2021-02-16 9:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210215162151.5655-3-cristian.dumitrescu@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=20210216093847.C2786C906@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).