From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Robin Jarry <rjarry@redhat.com>
Subject: |WARNING| pw138751 [PATCH v2] graph: expose node context as pointers
Date: Fri, 22 Mar 2024 17:32:36 +0100 (CET) [thread overview]
Message-ID: <20240322163236.5EEA51223F9@dpdk.org> (raw)
In-Reply-To: <20240322163130.671185-2-rjarry@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138751
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
next prev parent reply other threads:[~2024-03-22 16:32 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240322163130.671185-2-rjarry@redhat.com>
2024-03-22 16:18 ` |SUCCESS| " qemudev
2024-03-22 16:22 ` qemudev
2024-03-22 16:32 ` checkpatch [this message]
2024-03-22 17:45 ` |FAILURE| " 0-day Robot
2024-03-23 0:44 ` |SUCCESS| pw138751 [PATCH] [v2] graph: expose node context as pointe dpdklab
2024-03-23 0:45 ` dpdklab
2024-03-23 0:45 ` dpdklab
2024-03-23 0:46 ` dpdklab
2024-03-23 0:46 ` dpdklab
2024-03-23 0:46 ` dpdklab
2024-03-23 0:47 ` dpdklab
2024-03-23 0:47 ` dpdklab
2024-03-23 0:48 ` dpdklab
2024-03-23 0:48 ` dpdklab
2024-03-23 0:49 ` dpdklab
2024-03-23 0:49 ` dpdklab
2024-03-23 0:51 ` dpdklab
2024-03-23 0:52 ` dpdklab
2024-03-23 0:55 ` dpdklab
2024-03-23 0:57 ` dpdklab
2024-03-23 0:57 ` dpdklab
2024-03-23 0:58 ` dpdklab
2024-03-23 0:58 ` dpdklab
2024-03-23 1:00 ` dpdklab
2024-03-23 1:01 ` dpdklab
2024-03-23 1:01 ` dpdklab
2024-03-23 1:02 ` dpdklab
2024-03-23 1:05 ` dpdklab
2024-03-23 1:12 ` dpdklab
2024-03-23 1:16 ` dpdklab
2024-03-23 1:20 ` dpdklab
2024-03-23 1:20 ` dpdklab
2024-03-23 1:21 ` dpdklab
2024-03-23 1:21 ` dpdklab
2024-03-23 1:25 ` dpdklab
2024-03-23 1:30 ` dpdklab
2024-03-23 1:30 ` dpdklab
2024-03-23 1:31 ` dpdklab
2024-03-23 1:34 ` dpdklab
2024-03-23 1:35 ` dpdklab
2024-03-23 1:36 ` dpdklab
2024-03-23 1:36 ` dpdklab
2024-03-23 1:37 ` dpdklab
2024-03-23 1:37 ` dpdklab
2024-03-23 1:38 ` dpdklab
2024-03-23 1:39 ` dpdklab
2024-03-23 1:40 ` dpdklab
2024-03-23 1:40 ` dpdklab
2024-03-23 1:40 ` dpdklab
2024-03-23 1:40 ` dpdklab
2024-03-23 1:44 ` dpdklab
2024-03-23 1:44 ` dpdklab
2024-03-23 1:45 ` dpdklab
2024-03-23 1:45 ` dpdklab
2024-03-23 1:45 ` dpdklab
2024-03-23 1:45 ` dpdklab
2024-03-23 1:46 ` dpdklab
2024-03-23 1:47 ` dpdklab
2024-03-23 1:47 ` dpdklab
2024-03-23 1:48 ` dpdklab
2024-03-23 1:49 ` dpdklab
2024-03-23 1:49 ` dpdklab
2024-03-23 1:50 ` dpdklab
2024-03-23 1:51 ` dpdklab
2024-03-23 1:51 ` dpdklab
2024-03-23 1:52 ` dpdklab
2024-03-23 1:52 ` dpdklab
2024-03-23 1:53 ` dpdklab
2024-03-23 1:53 ` dpdklab
2024-03-23 1:57 ` dpdklab
2024-03-23 2:00 ` dpdklab
2024-03-23 2:07 ` dpdklab
2024-03-23 2:25 ` dpdklab
2024-03-23 3:05 ` dpdklab
2024-03-23 3:09 ` dpdklab
2024-03-23 3:22 ` dpdklab
2024-03-23 6:25 ` dpdklab
2024-03-24 19:09 ` dpdklab
2024-03-24 19:45 ` 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=20240322163236.5EEA51223F9@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).