From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138371 [PATCH v2 6/6] app/testpmd: enhance getopt_long usage
Date: Thu, 14 Mar 2024 10:19:03 +0100 (CET) [thread overview]
Message-ID: <20240314091903.EBCF81223F3@dpdk.org> (raw)
In-Reply-To: <20240314091708.1542769-7-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138371
_coding style OK_
next prev parent reply other threads:[~2024-03-14 9:19 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314091708.1542769-7-david.marchand@redhat.com>
2024-03-14 8:55 ` |SUCCESS| pw138366-138371 " qemudev
2024-03-14 8:59 ` qemudev
2024-03-14 9:19 ` checkpatch [this message]
2024-03-14 10:03 ` |SUCCESS| pw138371 " 0-day Robot
2024-03-14 11:01 ` |SUCCESS| pw138366-138371 [PATCH] [v2,6/6] app/testpmd: enhance geto dpdklab
2024-03-14 11:02 ` dpdklab
2024-03-14 11:11 ` dpdklab
2024-03-14 11:12 ` dpdklab
2024-03-14 11:24 ` dpdklab
2024-03-14 11:25 ` dpdklab
2024-03-14 11:25 ` dpdklab
2024-03-14 11:28 ` dpdklab
2024-03-14 11:33 ` dpdklab
2024-03-14 11:34 ` dpdklab
2024-03-14 11:38 ` dpdklab
2024-03-14 11:38 ` dpdklab
2024-03-14 11:39 ` dpdklab
2024-03-14 11:40 ` dpdklab
2024-03-14 11:40 ` dpdklab
2024-03-14 11:40 ` dpdklab
2024-03-14 11:41 ` dpdklab
2024-03-14 11:41 ` dpdklab
2024-03-14 11:41 ` dpdklab
2024-03-14 11:42 ` dpdklab
2024-03-14 11:42 ` dpdklab
2024-03-14 11:42 ` dpdklab
2024-03-14 11:43 ` dpdklab
2024-03-14 11:44 ` dpdklab
2024-03-14 11:44 ` dpdklab
2024-03-14 11:44 ` dpdklab
2024-03-14 11:44 ` dpdklab
2024-03-14 11:46 ` dpdklab
2024-03-14 11:46 ` dpdklab
2024-03-14 11:47 ` dpdklab
2024-03-14 11:47 ` dpdklab
2024-03-14 11:47 ` dpdklab
2024-03-14 11:47 ` dpdklab
2024-03-14 11:47 ` dpdklab
2024-03-14 11:48 ` dpdklab
2024-03-14 11:48 ` dpdklab
2024-03-14 11:48 ` dpdklab
2024-03-14 11:49 ` dpdklab
2024-03-14 11:49 ` dpdklab
2024-03-14 11:49 ` dpdklab
2024-03-14 11:50 ` dpdklab
2024-03-14 11:51 ` dpdklab
2024-03-14 11:52 ` dpdklab
2024-03-14 11:52 ` dpdklab
2024-03-14 11:52 ` dpdklab
2024-03-14 11:52 ` dpdklab
2024-03-14 11:52 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 11:54 ` dpdklab
2024-03-14 11:54 ` dpdklab
2024-03-14 11:56 ` dpdklab
2024-03-14 11:57 ` dpdklab
2024-03-14 11:58 ` dpdklab
2024-03-14 11:58 ` dpdklab
2024-03-14 11:59 ` dpdklab
2024-03-14 11:59 ` dpdklab
2024-03-14 11:59 ` dpdklab
2024-03-14 11:59 ` dpdklab
2024-03-14 12:03 ` dpdklab
2024-03-14 12:08 ` dpdklab
2024-03-14 12:15 ` dpdklab
2024-03-14 12:18 ` dpdklab
2024-03-14 12:19 ` dpdklab
2024-03-14 12:26 ` dpdklab
2024-03-14 12:54 ` dpdklab
2024-03-14 12:56 ` dpdklab
2024-03-14 13:00 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-18 3:48 ` dpdklab
2024-03-18 4:42 ` 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=20240314091903.EBCF81223F3@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).