automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw137761 [PATCH v2 71/71] examples: replace use of fixed size rte_memcpy
Date: Fri,  1 Mar 2024 18:26:00 +0100 (CET)	[thread overview]
Message-ID: <20240301172600.C620E122335@dpdk.org> (raw)
In-Reply-To: <20240301171707.95242-72-stephen@networkplumber.org>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#148: FILE: examples/ptpclient/ptpclient.c:362:
+		memcpy(&ptp_data->master_clock_id,

WARNING:LONG_LINE: line length of 111 exceeds 100 columns
#178: FILE: examples/vhost/main.c:409:
+	(void)(memcpy(&eth_conf->rx_adv_conf.vmdq_rx_conf, &conf, sizeof(eth_conf->rx_adv_conf.vmdq_rx_conf)));

WARNING:LONG_LINE: line length of 111 exceeds 100 columns
#202: FILE: examples/vmdq/main.c:154:
+	(void)(memcpy(&eth_conf->rx_adv_conf.vmdq_rx_conf, &conf, sizeof(eth_conf->rx_adv_conf.vmdq_rx_conf)));

total: 0 errors, 3 warnings, 103 lines checked

       reply	other threads:[~2024-03-01 17:26 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301171707.95242-72-stephen@networkplumber.org>
2024-03-01 17:26 ` checkpatch [this message]
2024-03-01 18:24 ` |SUCCESS| " 0-day Robot
2024-03-01 21:01 ` |SUCCESS| pw137691-137761 [PATCH] [v2,71/71] examples: replace use o dpdklab
2024-03-01 21:06 ` dpdklab
2024-03-01 21:09 ` |FAILURE| " dpdklab
2024-03-01 21:10 ` |SUCCESS| " dpdklab
2024-03-01 21:15 ` |FAILURE| " dpdklab
2024-03-01 21:25 ` |SUCCESS| " dpdklab
2024-03-01 21:34 ` dpdklab
2024-03-01 21:36 ` dpdklab
2024-03-01 21:37 ` dpdklab
2024-03-01 21:46 ` dpdklab
2024-03-01 21:47 ` |FAILURE| " dpdklab
2024-03-01 21:48 ` |SUCCESS| " dpdklab
2024-03-01 21:49 ` dpdklab
2024-03-01 21:52 ` dpdklab
2024-03-01 21:54 ` dpdklab
2024-03-01 21:55 ` dpdklab
2024-03-01 22:01 ` dpdklab
2024-03-01 22:15 ` dpdklab
2024-03-01 23:16 ` dpdklab
2024-03-01 23:16 ` dpdklab
2024-03-01 23:18 ` |FAILURE| " dpdklab
2024-03-01 23:19 ` |SUCCESS| " dpdklab
2024-03-01 23:59 ` dpdklab
2024-03-02  0:02 ` dpdklab
2024-03-02  0:02 ` dpdklab
2024-03-02  0:03 ` dpdklab
2024-03-02  0:04 ` dpdklab
2024-03-02  0:09 ` dpdklab
2024-03-02  0:11 ` dpdklab
2024-03-02  0:11 ` dpdklab
2024-03-02  0:11 ` dpdklab
2024-03-02  0:11 ` dpdklab
2024-03-02  0:12 ` dpdklab
2024-03-02  0:13 ` dpdklab
2024-03-02  0:13 ` dpdklab
2024-03-02  0:14 ` dpdklab
2024-03-02  0:15 ` dpdklab
2024-03-02  0:15 ` dpdklab
2024-03-02  0:16 ` dpdklab
2024-03-02  0:16 ` dpdklab
2024-03-02  0:16 ` dpdklab
2024-03-02  0:16 ` dpdklab
2024-03-02  0:17 ` dpdklab
2024-03-02  0:17 ` dpdklab
2024-03-02  0:36 ` dpdklab
2024-03-02  0:37 ` dpdklab
2024-03-02  0:38 ` dpdklab
2024-03-02  0:38 ` dpdklab
2024-03-02  0:39 ` dpdklab
2024-03-02  0:46 ` dpdklab
2024-03-02  0:46 ` dpdklab
2024-03-02  0:46 ` dpdklab
2024-03-02  0:55 ` dpdklab
2024-03-02  0:56 ` dpdklab
2024-03-02  0:56 ` dpdklab
2024-03-02  0:57 ` dpdklab
2024-03-02  0:58 ` dpdklab
2024-03-02  0:58 ` dpdklab
2024-03-02  0:59 ` dpdklab
2024-03-02  0:59 ` dpdklab
2024-03-02  1:00 ` dpdklab
2024-03-02  1:02 ` dpdklab
2024-03-02  1:03 ` dpdklab
2024-03-02  1:05 ` dpdklab
2024-03-02  1:07 ` dpdklab
2024-03-02  1:11 ` dpdklab
2024-03-02  1:12 ` dpdklab
2024-03-02  1:25 ` dpdklab
2024-03-02  2:34 ` |SUCCESS| pw137691-137761 [PATCH v2 71/71] examples: replace use of fixed size rte_memcpy qemudev
2024-03-02  2:38 ` qemudev
2024-03-02  3:51 ` |SUCCESS| pw137691-137761 [PATCH] [v2,71/71] examples: replace use o dpdklab
2024-03-03  1:05 ` dpdklab
2024-03-04  6:06 ` dpdklab
2024-03-05 22:17 ` dpdklab
2024-03-05 22:50 ` dpdklab
2024-03-05 23:22 ` dpdklab

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=20240301172600.C620E122335@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=stephen@networkplumber.org \
    --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).