automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Subject: |WARNING| pw155579 [PATCH] [PATCH v5] app/testpmd: fix segfault in secondary process by monitoring primary
Date: Tue, 29 Jul 2025 08:38:54 +0200 (CEST)	[thread overview]
Message-ID: <20250729063855.634141251A0@dpdk.org> (raw)
In-Reply-To: <20250729063919.3554143-3-14pwcse1224@uetpeshawar.edu.pk>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#104: 
This patch adds a mechanism in testpmd to monitor the primary process from the

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 24)
#219: FILE: lib/ethdev/rte_ethdev.c:4082:
+	if (rte_eal_process_type() == RTE_PROC_SECONDARY &&
[...]
+			RTE_ETHDEV_LOG_LINE(ERR,

total: 0 errors, 2 warnings, 105 lines checked

  parent reply	other threads:[~2025-07-29  6:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250729063919.3554143-3-14pwcse1224@uetpeshawar.edu.pk>
2025-07-29  6:05 ` |SUCCESS| " qemudev
2025-07-29  6:10 ` qemudev
2025-07-29  6:38 ` checkpatch [this message]
2025-07-29  7:12 ` |PENDING| pw155579 [PATCH] [v5] app/testpmd: fix segfault in seconda dpdklab
2025-07-29  7:15 ` dpdklab
2025-07-29  7:16 ` |FAILURE| " dpdklab
2025-07-29  7:17 ` |PENDING| " dpdklab
2025-07-29  7:18 ` |SUCCESS| " dpdklab
2025-07-29  7:19 ` |FAILURE| " dpdklab
2025-07-29  7:19 ` dpdklab
2025-07-29  7:20 ` dpdklab
2025-07-29  7:22 ` dpdklab
2025-07-29  7:24 ` |SUCCESS| " dpdklab
2025-07-29  7:32 ` dpdklab
2025-07-29  7:35 ` dpdklab
2025-07-29  7:35 ` dpdklab
2025-07-29  7:43 ` |FAILURE| pw155579 [PATCH] [PATCH v5] app/testpmd: fix segfault in secondary process by monitoring primary 0-day Robot
2025-07-29  7:47 ` |SUCCESS| pw155579 [PATCH] [v5] app/testpmd: fix segfault in seconda dpdklab
2025-07-29  8:07 ` dpdklab
2025-07-29  8:10 ` |FAILURE| " dpdklab
2025-07-29  8:42 ` |SUCCESS| " dpdklab
2025-07-29  9:34 ` |PENDING| " dpdklab
2025-07-29 11:16 ` |FAILURE| " dpdklab
2025-07-29 11:42 ` |SUCCESS| " dpdklab
2025-07-29 14:23 ` 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=20250729063855.634141251A0@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=14pwcse1224@uetpeshawar.edu.pk \
    --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).