From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw157015 [PATCH] net/zxdh: avoid use of rte_memcpy
Date: Fri, 26 Sep 2025 20:07:48 +0200 (CEST) [thread overview]
Message-ID: <20250926180748.70FF3124247@dpdk.org> (raw)
In-Reply-To: <20250926181017.470585-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/157015
_coding style issues_
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#129: FILE: drivers/net/zxdh/zxdh_flow.c:1334:
+ memcpy((uint32_t *)key_mask->src_ip + 3, &ipv4_mask->hdr.src_addr, 4);
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#130: FILE: drivers/net/zxdh/zxdh_flow.c:1335:
+ memcpy((uint32_t *)key_mask->dst_ip + 3, &ipv4_mask->hdr.dst_addr, 4);
total: 0 errors, 2 warnings, 0 checks, 115 lines checked
next prev parent reply other threads:[~2025-09-26 18:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250926181017.470585-1-stephen@networkplumber.org>
2025-09-26 17:35 ` |SUCCESS| " qemudev
2025-09-26 17:40 ` qemudev
2025-09-26 18:07 ` checkpatch [this message]
2025-09-26 18:43 ` |PENDING| " dpdklab
2025-09-26 18:47 ` |SUCCESS| " dpdklab
2025-09-26 18:49 ` dpdklab
2025-09-26 18:51 ` dpdklab
2025-09-26 18:56 ` dpdklab
2025-09-26 19:21 ` dpdklab
2025-09-26 19:22 ` |PENDING| " dpdklab
2025-09-26 19:36 ` |SUCCESS| " dpdklab
2025-09-26 19:46 ` |PENDING| " dpdklab
2025-09-26 19:59 ` |SUCCESS| " dpdklab
2025-09-26 20:00 ` dpdklab
2025-09-26 20:53 ` |PENDING| " dpdklab
2025-09-26 21:12 ` |SUCCESS| " dpdklab
2025-09-26 21:39 ` dpdklab
2025-09-26 21:48 ` dpdklab
2025-09-26 21:55 ` dpdklab
2025-09-26 22:06 ` dpdklab
2025-09-26 22:07 ` dpdklab
2025-09-26 22:11 ` dpdklab
2025-09-26 22:41 ` dpdklab
2025-09-27 1:39 ` dpdklab
2025-09-27 3:32 ` 0-day Robot
2025-09-27 3:32 ` 0-day Robot
2025-09-27 11:21 ` 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=20250926180748.70FF3124247@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).