From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>
Subject: |WARNING| pw138765 [PATCH v3] graph: expose node context as pointers
Date: Mon, 25 Mar 2024 11:06:01 +0100 (CET) [thread overview]
Message-ID: <20240325100601.C60DD1223FA@dpdk.org> (raw)
In-Reply-To: <20240325100500.694748-2-rjarry@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138765
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
next prev parent reply other threads:[~2024-03-25 10:06 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240325100500.694748-2-rjarry@redhat.com>
2024-03-25 9:42 ` |SUCCESS| " qemudev
2024-03-25 9:47 ` qemudev
2024-03-25 10:06 ` checkpatch [this message]
2024-03-25 10:49 ` |SUCCESS| pw138765 [PATCH] [v3] graph: expose node context as pointe dpdklab
2024-03-25 10:50 ` dpdklab
2024-03-25 10:58 ` dpdklab
2024-03-25 11:03 ` dpdklab
2024-03-25 11:04 ` dpdklab
2024-03-25 11:04 ` dpdklab
2024-03-25 11:04 ` |FAILURE| pw138765 [PATCH v3] graph: expose node context as pointers 0-day Robot
2024-03-25 11:05 ` |SUCCESS| pw138765 [PATCH] [v3] graph: expose node context as pointe dpdklab
2024-03-25 11:06 ` dpdklab
2024-03-25 11:06 ` dpdklab
2024-03-25 11:07 ` dpdklab
2024-03-25 11:07 ` dpdklab
2024-03-25 11:07 ` dpdklab
2024-03-25 11:07 ` dpdklab
2024-03-25 11:07 ` dpdklab
2024-03-25 11:07 ` dpdklab
2024-03-25 11:08 ` dpdklab
2024-03-25 11:08 ` |FAILURE| " dpdklab
2024-03-25 11:09 ` |SUCCESS| " dpdklab
2024-03-25 11:09 ` dpdklab
2024-03-25 11:14 ` dpdklab
2024-03-25 11:14 ` |FAILURE| " dpdklab
2024-03-25 11:15 ` |SUCCESS| " dpdklab
2024-03-25 11:15 ` dpdklab
2024-03-25 11:15 ` dpdklab
2024-03-25 11:15 ` dpdklab
2024-03-25 11:15 ` dpdklab
2024-03-25 11:15 ` |WARNING| " dpdklab
2024-03-25 11:16 ` |SUCCESS| " dpdklab
2024-03-25 11:16 ` |FAILURE| " dpdklab
2024-03-25 11:16 ` |SUCCESS| " dpdklab
2024-03-25 11:16 ` dpdklab
2024-03-25 11:16 ` |FAILURE| " dpdklab
2024-03-25 11:16 ` |SUCCESS| " dpdklab
2024-03-25 11:17 ` dpdklab
2024-03-25 11:17 ` |FAILURE| " dpdklab
2024-03-25 11:17 ` |SUCCESS| " dpdklab
2024-03-25 11:17 ` dpdklab
2024-03-25 11:17 ` dpdklab
2024-03-25 11:17 ` dpdklab
2024-03-25 11:17 ` |WARNING| " dpdklab
2024-03-25 11:18 ` |SUCCESS| " dpdklab
2024-03-25 11:18 ` dpdklab
2024-03-25 11:18 ` dpdklab
2024-03-25 11:18 ` dpdklab
2024-03-25 11:19 ` dpdklab
2024-03-25 11:19 ` dpdklab
2024-03-25 11:19 ` dpdklab
2024-03-25 11:19 ` dpdklab
2024-03-25 11:20 ` dpdklab
2024-03-25 11:20 ` dpdklab
2024-03-25 11:21 ` dpdklab
2024-03-25 11:21 ` |WARNING| " dpdklab
2024-03-25 11:22 ` dpdklab
2024-03-25 11:23 ` |SUCCESS| " dpdklab
2024-03-25 11:23 ` |WARNING| " dpdklab
2024-03-25 11:23 ` dpdklab
2024-03-25 11:23 ` |SUCCESS| " dpdklab
2024-03-25 11:24 ` |WARNING| " dpdklab
2024-03-25 11:25 ` |SUCCESS| " dpdklab
2024-03-25 11:25 ` dpdklab
2024-03-25 11:26 ` dpdklab
2024-03-25 11:26 ` dpdklab
2024-03-25 11:26 ` dpdklab
2024-03-25 11:38 ` dpdklab
2024-03-25 11:41 ` |WARNING| " dpdklab
2024-03-25 11:42 ` |FAILURE| " dpdklab
2024-03-25 11:43 ` |SUCCESS| " dpdklab
2024-03-25 11:43 ` |FAILURE| " dpdklab
2024-03-25 11:43 ` dpdklab
2024-03-25 11:44 ` |WARNING| " dpdklab
2024-03-25 11:46 ` dpdklab
2024-03-25 11:53 ` |FAILURE| " dpdklab
2024-03-25 12:05 ` dpdklab
2024-03-25 12:23 ` dpdklab
2024-03-25 12:27 ` dpdklab
2024-03-25 12:42 ` |SUCCESS| " dpdklab
2024-03-25 13: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=20240325100601.C60DD1223FA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rjarry@redhat.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).