automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shaokai Zhang <felix.zhang@jaguarmicro.com>
Subject: |WARNING| pw152490 [PATCH] net/af_packet: register supported param fanout mode
Date: Thu, 20 Mar 2025 09:15:52 +0100 (CET)	[thread overview]
Message-ID: <20250320081552.8BC77123DB3@dpdk.org> (raw)
In-Reply-To: <20250320081503.5505-1-felix.zhang@jaguarmicro.com>

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

_coding style issues_


ERROR:CODE_INDENT: code indent should use tabs where possible
#124: FILE: drivers/net/af_packet/rte_eth_af_packet.c:794:
+                       unsigned int qdisc_bypass,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#124: FILE: drivers/net/af_packet/rte_eth_af_packet.c:794:
+                       unsigned int qdisc_bypass,$

ERROR:CODE_INDENT: code indent should use tabs where possible
#125: FILE: drivers/net/af_packet/rte_eth_af_packet.c:795:
+                       const char *fanout_mode,$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#125: FILE: drivers/net/af_packet/rte_eth_af_packet.c:795:
+                       const char *fanout_mode,$

total: 2 errors, 2 warnings, 0 checks, 27 lines checked

  parent reply	other threads:[~2025-03-20  8:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250320081503.5505-1-felix.zhang@jaguarmicro.com>
2025-03-20  7:49 ` |SUCCESS| " qemudev
2025-03-20  7:53 ` qemudev
2025-03-20  8:15 ` checkpatch [this message]
2025-03-20  8:53 ` |PENDING| pw152490 [PATCH] net/af_packet: register supported param f dpdklab
2025-03-20  9:01 ` |SUCCESS| " dpdklab
2025-03-20  9:04 ` |SUCCESS| pw152490 [PATCH] net/af_packet: register supported param fanout mode 0-day Robot
2025-03-20  9:05 ` |SUCCESS| pw152490 [PATCH] net/af_packet: register supported param f dpdklab
2025-03-20  9:14 ` |PENDING| " dpdklab
2025-03-20  9:15 ` |SUCCESS| " dpdklab
2025-03-20  9:21 ` dpdklab
2025-03-20  9:22 ` dpdklab
2025-03-20  9:26 ` dpdklab
2025-03-20  9:28 ` dpdklab
2025-03-20  9:30 ` dpdklab
2025-03-20  9:35 ` dpdklab
2025-03-20  9:39 ` dpdklab
2025-03-20  9:39 ` |PENDING| " dpdklab
2025-03-20  9:40 ` |SUCCESS| " dpdklab
2025-03-20  9:40 ` dpdklab
2025-03-20  9:41 ` dpdklab
2025-03-20 10:07 ` dpdklab
2025-03-20 10:17 ` dpdklab
2025-03-20 10:38 ` dpdklab
2025-03-20 10:38 ` dpdklab
2025-03-20 10:57 ` dpdklab
2025-03-20 12:52 ` dpdklab
2025-03-20 12:56 ` 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=20250320081552.8BC77123DB3@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=felix.zhang@jaguarmicro.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).