From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw137400 [PATCH] ethdev: fix coverity issue
Date: Tue, 27 Feb 2024 20:39:03 +0100 (CET) [thread overview]
Message-ID: <20240227193903.9B23D122320@dpdk.org> (raw)
In-Reply-To: <20240227193828.18612-1-hkalra@marvell.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/137400
_coding style OK_
next prev parent reply other threads:[~2024-02-27 19:39 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227193828.18612-1-hkalra@marvell.com>
2024-02-27 19:17 ` qemudev
2024-02-27 19:22 ` qemudev
2024-02-27 19:39 ` checkpatch [this message]
2024-02-27 20:45 ` 0-day Robot
2024-02-28 0:58 ` dpdklab
2024-02-28 1:00 ` dpdklab
2024-02-28 1:10 ` dpdklab
2024-02-28 1:28 ` dpdklab
2024-02-28 1:29 ` dpdklab
2024-02-28 1:29 ` dpdklab
2024-02-28 1:30 ` dpdklab
2024-02-28 1:36 ` dpdklab
2024-02-28 1:37 ` dpdklab
2024-02-28 1:38 ` dpdklab
2024-02-28 1:39 ` dpdklab
2024-02-28 1:41 ` dpdklab
2024-02-28 1:41 ` dpdklab
2024-02-28 1:52 ` dpdklab
2024-02-28 2:23 ` dpdklab
2024-02-28 2:25 ` dpdklab
2024-02-28 2:36 ` dpdklab
2024-02-28 2:37 ` dpdklab
2024-02-28 2:42 ` dpdklab
2024-02-28 2:54 ` dpdklab
2024-02-28 2:56 ` dpdklab
2024-02-28 2:56 ` dpdklab
2024-02-28 2:56 ` dpdklab
2024-02-28 2:57 ` dpdklab
2024-02-28 2:57 ` dpdklab
2024-02-28 2:58 ` dpdklab
2024-02-28 3:00 ` dpdklab
2024-02-28 3:01 ` dpdklab
2024-02-28 3:03 ` dpdklab
2024-02-28 3:03 ` dpdklab
2024-02-28 3:03 ` dpdklab
2024-02-28 3:04 ` dpdklab
2024-02-28 3:04 ` dpdklab
2024-02-28 3:04 ` dpdklab
2024-02-28 3:05 ` dpdklab
2024-02-28 3:05 ` dpdklab
2024-02-28 3:06 ` dpdklab
2024-02-28 3:07 ` dpdklab
2024-02-28 3:11 ` dpdklab
2024-02-28 3:27 ` dpdklab
2024-02-28 3:31 ` dpdklab
2024-02-28 3:33 ` dpdklab
2024-02-28 3:33 ` dpdklab
2024-02-28 3:36 ` dpdklab
2024-02-28 3:42 ` dpdklab
2024-02-28 3:44 ` dpdklab
2024-02-28 3:53 ` dpdklab
2024-02-28 3:55 ` dpdklab
2024-02-28 4:04 ` dpdklab
2024-02-28 4:04 ` dpdklab
2024-02-28 4:05 ` dpdklab
2024-02-28 4:05 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:07 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:21 ` dpdklab
2024-02-28 4:23 ` dpdklab
2024-02-28 9:53 ` dpdklab
2024-02-28 13:12 ` dpdklab
2024-02-28 13:19 ` dpdklab
2024-02-28 21:19 ` dpdklab
2024-02-29 15:15 ` dpdklab
2024-02-29 16:19 ` dpdklab
2024-02-29 16:22 ` dpdklab
2024-02-29 16:27 ` dpdklab
2024-02-29 16:29 ` 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=20240227193903.9B23D122320@dpdk.org \
--to=checkpatch@dpdk.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).