From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Subject: |WARNING| pw155372 [PATCH] net/ice: fix segfault in secondary process by validating dev_private pointer
Date: Mon, 21 Jul 2025 12:54:27 +0200 (CEST) [thread overview]
Message-ID: <20250721105427.94DD112530F@dpdk.org> (raw)
In-Reply-To: <20250721105522.1019515-1-14pwcse1224@uetpeshawar.edu.pk>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155372
_coding style issues_
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 24)
#112: FILE: drivers/net/intel/ice/ice_ethdev.c:4093:
+ if (rte_eal_process_type() == RTE_PROC_SECONDARY &&
[...]
+ PMD_DRV_LOG(ERR,
total: 0 errors, 1 warnings, 0 checks, 15 lines checked
next prev parent reply other threads:[~2025-07-21 10:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250721105522.1019515-1-14pwcse1224@uetpeshawar.edu.pk>
2025-07-21 10:21 ` |SUCCESS| " qemudev
2025-07-21 10:26 ` qemudev
2025-07-21 10:54 ` checkpatch [this message]
2025-07-21 11:43 ` 0-day Robot
2025-07-21 11:43 ` |SUCCESS| pw155372 [PATCH] net/ice: fix segfault in secondary proces dpdklab
2025-07-21 11:47 ` dpdklab
2025-07-21 11:52 ` |PENDING| " dpdklab
2025-07-21 11:56 ` |SUCCESS| " dpdklab
2025-07-21 11:57 ` dpdklab
2025-07-21 12:01 ` |PENDING| " dpdklab
2025-07-21 12:06 ` |SUCCESS| " dpdklab
2025-07-21 12:08 ` dpdklab
2025-07-21 12:16 ` |PENDING| " dpdklab
2025-07-21 13:30 ` |SUCCESS| " dpdklab
2025-07-21 14:43 ` dpdklab
2025-07-21 14:48 ` |PENDING| " dpdklab
2025-07-21 16:00 ` |SUCCESS| " dpdklab
2025-07-21 16:00 ` dpdklab
2025-07-21 18:34 ` 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=20250721105427.94DD112530F@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).