From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw139064 [PATCH v3 30/30] examples: replace use of fixed size rte_memcpy
Date: Wed, 3 Apr 2024 00:00:54 +0200 (CEST) [thread overview]
Message-ID: <20240402220054.4AC841223FE@dpdk.org> (raw)
In-Reply-To: <20240402215502.278838-31-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139064
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#344: FILE: examples/ptpclient/ptpclient.c:365:
+ memcpy(&ptp_data->master_clock_id,
WARNING:LONG_LINE: line length of 111 exceeds 100 columns
#447: FILE: examples/vmdq/main.c:154:
+ (void)(memcpy(ð_conf->rx_adv_conf.vmdq_rx_conf, &conf, sizeof(eth_conf->rx_adv_conf.vmdq_rx_conf)));
total: 0 errors, 2 warnings, 230 lines checked
next prev parent reply other threads:[~2024-04-02 22:00 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240402215502.278838-31-stephen@networkplumber.org>
2024-04-02 21:37 ` |SUCCESS| pw139035-139064 " qemudev
2024-04-02 21:41 ` qemudev
2024-04-02 22:00 ` checkpatch [this message]
2024-04-02 23:05 ` |SUCCESS| pw139064 " 0-day Robot
2024-04-03 3:34 ` |SUCCESS| pw139035-139064 [PATCH] [v3,30/30] examples: replace use o dpdklab
2024-04-03 3:35 ` dpdklab
2024-04-03 3:36 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:41 ` dpdklab
2024-04-03 3:42 ` dpdklab
2024-04-03 3:42 ` dpdklab
2024-04-03 3:43 ` dpdklab
2024-04-03 3:43 ` dpdklab
2024-04-03 3:43 ` dpdklab
2024-04-03 3:44 ` dpdklab
2024-04-03 3:44 ` dpdklab
2024-04-03 3:44 ` dpdklab
2024-04-03 3:45 ` dpdklab
2024-04-03 3:48 ` dpdklab
2024-04-03 3:48 ` dpdklab
2024-04-03 3:49 ` dpdklab
2024-04-03 3:51 ` dpdklab
2024-04-03 3:55 ` dpdklab
2024-04-03 3:56 ` dpdklab
2024-04-03 3:56 ` dpdklab
2024-04-03 3:57 ` dpdklab
2024-04-03 3:57 ` dpdklab
2024-04-03 4:00 ` dpdklab
2024-04-03 4:04 ` dpdklab
2024-04-03 4:05 ` dpdklab
2024-04-03 4:05 ` dpdklab
2024-04-03 4:05 ` dpdklab
2024-04-03 4:11 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:21 ` dpdklab
2024-04-03 4:22 ` dpdklab
2024-04-03 4:22 ` dpdklab
2024-04-03 4:22 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:23 ` dpdklab
2024-04-03 4:24 ` dpdklab
2024-04-03 4:24 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:30 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:31 ` dpdklab
2024-04-03 4:32 ` dpdklab
2024-04-03 4:32 ` dpdklab
2024-04-03 4:33 ` dpdklab
2024-04-03 4:40 ` dpdklab
2024-04-03 4:41 ` dpdklab
2024-04-03 4:45 ` dpdklab
2024-04-03 4:46 ` dpdklab
2024-04-03 4:46 ` dpdklab
2024-04-03 4:46 ` dpdklab
2024-04-03 4:50 ` dpdklab
2024-04-03 4:50 ` dpdklab
2024-04-03 4:50 ` dpdklab
2024-04-03 4:51 ` dpdklab
2024-04-03 4:53 ` dpdklab
2024-04-03 4:53 ` dpdklab
2024-04-03 4:53 ` dpdklab
2024-04-03 4:59 ` dpdklab
2024-04-03 5:02 ` dpdklab
2024-04-03 5:03 ` dpdklab
2024-04-03 5:04 ` dpdklab
2024-04-03 5:05 ` dpdklab
2024-04-03 5:14 ` dpdklab
2024-04-03 5:16 ` dpdklab
2024-04-03 5:17 ` dpdklab
2024-04-03 5:32 ` dpdklab
2024-04-03 5:38 ` dpdklab
2024-04-03 5:39 ` dpdklab
2024-04-03 5:56 ` dpdklab
2024-04-03 7:01 ` dpdklab
2024-04-03 22:23 ` dpdklab
2024-04-03 22:27 ` dpdklab
2024-04-03 23:04 ` dpdklab
2024-04-03 23:44 ` dpdklab
2024-04-03 23:47 ` 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=20240402220054.4AC841223FE@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).