From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kiran Vedere <kiranv@nvidia.com>
Subject: |WARNING| pw140731 [PATCH] net/mlx5: add queue hardware object context dump
Date: Tue, 4 Jun 2024 23:12:38 +0200 (CEST) [thread overview]
Message-ID: <20240604211238.0E81712367B@dpdk.org> (raw)
In-Reply-To: <20240604211136.1616519-1-kiranv@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140731
_coding style issues_
Warning in drivers/net/mlx5/mlx5_testpmd.c:
Writing to stdout or stderr
next prev parent reply other threads:[~2024-06-04 21:12 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604211136.1616519-1-kiranv@nvidia.com>
2024-06-04 20:46 ` |SUCCESS| " qemudev
2024-06-04 20:50 ` qemudev
2024-06-04 21:12 ` checkpatch [this message]
2024-06-04 22:14 ` |SUCCESS| pw140731 [PATCH] net/mlx5: add queue hardware object conte dpdklab
2024-06-04 22:32 ` dpdklab
2024-06-04 22:32 ` dpdklab
2024-06-04 22:34 ` dpdklab
2024-06-04 22:34 ` dpdklab
2024-06-04 22:34 ` dpdklab
2024-06-04 22:35 ` dpdklab
2024-06-04 22:35 ` dpdklab
2024-06-04 22:35 ` dpdklab
2024-06-04 22:36 ` dpdklab
2024-06-04 22:36 ` dpdklab
2024-06-04 22:36 ` dpdklab
2024-06-04 22:37 ` dpdklab
2024-06-04 22:38 ` dpdklab
2024-06-04 22:39 ` dpdklab
2024-06-04 22:40 ` dpdklab
2024-06-04 22:41 ` dpdklab
2024-06-04 22:41 ` dpdklab
2024-06-04 22:41 ` dpdklab
2024-06-04 22:42 ` dpdklab
2024-06-04 22:53 ` dpdklab
2024-06-04 22:53 ` dpdklab
2024-06-04 22:53 ` dpdklab
2024-06-04 22:54 ` dpdklab
2024-06-04 22:54 ` dpdklab
2024-06-04 22:55 ` dpdklab
2024-06-04 23:03 ` dpdklab
2024-06-04 23:03 ` dpdklab
2024-06-04 23:03 ` dpdklab
2024-06-04 23:20 ` dpdklab
2024-06-04 23:21 ` dpdklab
2024-06-04 23:21 ` dpdklab
2024-06-04 23:21 ` dpdklab
2024-06-04 23:22 ` dpdklab
2024-06-04 23:22 ` dpdklab
2024-06-04 23:23 ` dpdklab
2024-06-04 23:23 ` dpdklab
2024-06-04 23:24 ` dpdklab
2024-06-04 23:24 ` dpdklab
2024-06-04 23:24 ` dpdklab
2024-06-04 23:25 ` dpdklab
2024-06-04 23:25 ` dpdklab
2024-06-04 23:26 ` dpdklab
2024-06-04 23:27 ` dpdklab
2024-06-04 23:27 ` dpdklab
2024-06-04 23:27 ` dpdklab
2024-06-04 23:28 ` dpdklab
2024-06-04 23:28 ` dpdklab
2024-06-04 23:28 ` dpdklab
2024-06-04 23:29 ` dpdklab
2024-06-04 23:29 ` dpdklab
2024-06-04 23:29 ` dpdklab
2024-06-04 23:30 ` dpdklab
2024-06-04 23:30 ` dpdklab
2024-06-04 23:30 ` dpdklab
2024-06-04 23:31 ` dpdklab
2024-06-04 23:31 ` dpdklab
2024-06-04 23:32 ` dpdklab
2024-06-04 23:32 ` dpdklab
2024-06-04 23:32 ` dpdklab
2024-06-04 23:34 ` dpdklab
2024-06-04 23:34 ` dpdklab
2024-06-04 23:35 ` dpdklab
2024-06-04 23:36 ` dpdklab
2024-06-04 23:36 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:38 ` dpdklab
2024-06-04 23:39 ` dpdklab
2024-06-04 23:40 ` dpdklab
2024-06-04 23:40 ` dpdklab
2024-06-04 23:42 ` dpdklab
2024-06-04 23:44 ` dpdklab
2024-06-04 23:45 ` dpdklab
2024-06-04 23:48 ` dpdklab
2024-06-04 23:50 ` dpdklab
2024-06-04 23:50 ` dpdklab
2024-06-04 23:52 ` dpdklab
2024-06-04 23:55 ` |WARNING| " dpdklab
2024-06-04 23:56 ` dpdklab
2024-06-04 23:56 ` dpdklab
2024-06-05 0:01 ` dpdklab
2024-06-05 0:04 ` dpdklab
2024-06-05 0:05 ` dpdklab
2024-06-05 0:06 ` dpdklab
2024-06-05 0:08 ` dpdklab
2024-06-05 0:10 ` dpdklab
2024-06-05 0:18 ` |SUCCESS| " dpdklab
2024-06-05 0:20 ` dpdklab
2024-06-05 0:28 ` |WARNING| " dpdklab
2024-06-05 0:44 ` |SUCCESS| " dpdklab
2024-06-05 0:58 ` |WARNING| " dpdklab
2024-06-05 1:06 ` |SUCCESS| " dpdklab
2024-06-05 1:49 ` dpdklab
2024-06-05 21:17 ` 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=20240604211238.0E81712367B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kiranv@nvidia.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).