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| pw137645 [PATCH 71/71] examples: replace use of fixed size rte_memcpy
Date: Fri,  1 Mar 2024 00:09:21 +0100 (CET)	[thread overview]
Message-ID: <20240229230921.AAE7A12232A@dpdk.org> (raw)
In-Reply-To: <20240229225936.483472-72-stephen@networkplumber.org>

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

_coding style issues_


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

WARNING:LONG_LINE: line length of 111 exceeds 100 columns
#168: 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
#184: FILE: examples/vmdq/main.c:155:
+	(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, 82 lines checked

  parent reply	other threads:[~2024-02-29 23:09 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240229225936.483472-72-stephen@networkplumber.org>
2024-02-29 22:47 ` |SUCCESS| pw137575-137645 " qemudev
2024-02-29 22:51 ` qemudev
2024-02-29 23:09 ` checkpatch [this message]
2024-03-01  0:05 ` |FAILURE| pw137645 " 0-day Robot
2024-03-01  0:59 ` |SUCCESS| pw137575-137645 [PATCH] [71/71] examples: replace use of f dpdklab
2024-03-01  0:59 ` dpdklab
2024-03-01  1:00 ` dpdklab
2024-03-01  1:02 ` dpdklab
2024-03-01  1:04 ` dpdklab
2024-03-01  1:04 ` dpdklab
2024-03-01  1:08 ` dpdklab
2024-03-01  1:09 ` dpdklab
2024-03-01  1:32 ` dpdklab
2024-03-01  1:45 ` dpdklab
2024-03-01  1:49 ` dpdklab
2024-03-01  1:50 ` dpdklab
2024-03-01  1:50 ` dpdklab
2024-03-01  1:53 ` dpdklab
2024-03-01  1:53 ` dpdklab
2024-03-01  1:57 ` dpdklab
2024-03-01  2:00 ` dpdklab
2024-03-01  2:09 ` dpdklab
2024-03-01  4:44 ` dpdklab
2024-03-01  4:46 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:48 ` dpdklab
2024-03-01  4:48 ` dpdklab
2024-03-01  4:49 ` dpdklab
2024-03-01  4:49 ` dpdklab
2024-03-01  4:49 ` dpdklab
2024-03-01  4:50 ` dpdklab
2024-03-01  4:50 ` dpdklab
2024-03-01  4:50 ` dpdklab
2024-03-01  4:51 ` dpdklab
2024-03-01  4:51 ` dpdklab
2024-03-01  4:51 ` dpdklab
2024-03-01  4:51 ` dpdklab
2024-03-01  4:51 ` dpdklab
2024-03-01  4:51 ` dpdklab
2024-03-01  4:51 ` dpdklab
2024-03-01  4:52 ` dpdklab
2024-03-01  4:52 ` dpdklab
2024-03-01  4:52 ` dpdklab
2024-03-01  4:52 ` dpdklab
2024-03-01  4:52 ` dpdklab
2024-03-01  4:53 ` dpdklab
2024-03-01  4:53 ` dpdklab
2024-03-01  4:53 ` dpdklab
2024-03-01  4:54 ` dpdklab
2024-03-01  4:54 ` dpdklab
2024-03-01  4:54 ` dpdklab
2024-03-01  4:55 ` dpdklab
2024-03-01  5:00 ` dpdklab
2024-03-01  5:09 ` dpdklab
2024-03-01  5:09 ` dpdklab
2024-03-01  5:18 ` dpdklab
2024-03-01  5:20 ` dpdklab
2024-03-01  5:21 ` dpdklab
2024-03-01  5:21 ` dpdklab
2024-03-01  5:22 ` dpdklab
2024-03-01  5:27 ` dpdklab
2024-03-01  5:33 ` dpdklab
2024-03-01  5:37 ` dpdklab
2024-03-01  6:14 ` dpdklab
2024-03-01  6:16 ` dpdklab
2024-03-01  9:30 ` dpdklab
2024-03-01 15:16 ` dpdklab
2024-03-01 15:21 ` dpdklab
2024-03-01 15:22 ` dpdklab
2024-03-01 15:26 ` dpdklab
2024-03-02 14:49 ` dpdklab
2024-03-04 11:56 ` dpdklab
2024-03-04 12:24 ` dpdklab
2024-03-04 12:54 ` 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=20240229230921.AAE7A12232A@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).