From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138123 [PATCH] build: pass cflags in subproject
Date: Fri, 8 Mar 2024 13:00:21 +0100 (CET) [thread overview]
Message-ID: <20240308120021.3DE1E1223EF@dpdk.org> (raw)
In-Reply-To: <20240308115839.320793-2-rjarry@redhat.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138123
_coding style OK_
next prev parent reply other threads:[~2024-03-08 12:00 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240308115839.320793-2-rjarry@redhat.com>
2024-03-08 11:36 ` qemudev
2024-03-08 11:41 ` qemudev
2024-03-08 12:00 ` checkpatch [this message]
2024-03-08 13:06 ` 0-day Robot
2024-03-08 13:19 ` dpdklab
2024-03-08 13:19 ` dpdklab
2024-03-08 13:20 ` dpdklab
2024-03-08 13:20 ` dpdklab
2024-03-08 13:21 ` dpdklab
2024-03-08 13:21 ` dpdklab
2024-03-08 13:22 ` dpdklab
2024-03-08 13:22 ` dpdklab
2024-03-08 13:23 ` dpdklab
2024-03-08 13:23 ` dpdklab
2024-03-08 13:23 ` dpdklab
2024-03-08 13:24 ` dpdklab
2024-03-08 13:24 ` dpdklab
2024-03-08 13:24 ` dpdklab
2024-03-08 13:24 ` dpdklab
2024-03-08 13:25 ` dpdklab
2024-03-08 13:25 ` dpdklab
2024-03-08 13:25 ` dpdklab
2024-03-08 13:25 ` dpdklab
2024-03-08 13:25 ` dpdklab
2024-03-08 13:25 ` dpdklab
2024-03-08 13:26 ` dpdklab
2024-03-08 13:26 ` dpdklab
2024-03-08 13:27 ` dpdklab
2024-03-08 13:27 ` dpdklab
2024-03-08 13:27 ` dpdklab
2024-03-08 13:27 ` dpdklab
2024-03-08 13:27 ` dpdklab
2024-03-08 13:27 ` dpdklab
2024-03-08 13:28 ` dpdklab
2024-03-08 13:28 ` dpdklab
2024-03-08 13:28 ` dpdklab
2024-03-08 13:28 ` dpdklab
2024-03-08 13:28 ` dpdklab
2024-03-08 13:29 ` dpdklab
2024-03-08 13:29 ` dpdklab
2024-03-08 13:29 ` dpdklab
2024-03-08 13:29 ` dpdklab
2024-03-08 13:29 ` dpdklab
2024-03-08 13:29 ` dpdklab
2024-03-08 13:29 ` dpdklab
2024-03-08 13:30 ` dpdklab
2024-03-08 13:30 ` dpdklab
2024-03-08 13:30 ` dpdklab
2024-03-08 13:30 ` dpdklab
2024-03-08 13:30 ` dpdklab
2024-03-08 13:30 ` dpdklab
2024-03-08 13:31 ` dpdklab
2024-03-08 13:31 ` dpdklab
2024-03-08 13:31 ` dpdklab
2024-03-08 13:32 ` dpdklab
2024-03-08 13:32 ` dpdklab
2024-03-08 13:32 ` dpdklab
2024-03-08 13:32 ` dpdklab
2024-03-08 13:35 ` dpdklab
2024-03-08 13:36 ` dpdklab
2024-03-08 13:36 ` dpdklab
2024-03-08 13:36 ` dpdklab
2024-03-08 13:37 ` dpdklab
2024-03-08 13:42 ` dpdklab
2024-03-08 13:42 ` dpdklab
2024-03-08 13:44 ` dpdklab
2024-03-08 13:44 ` dpdklab
2024-03-08 13:52 ` dpdklab
2024-03-08 13:53 ` dpdklab
2024-03-08 13:56 ` dpdklab
2024-03-08 14:01 ` dpdklab
2024-03-08 14:04 ` dpdklab
2024-03-08 14:44 ` dpdklab
2024-03-08 15:38 ` dpdklab
2024-03-13 5:27 ` dpdklab
2024-03-13 5:50 ` 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=20240308120021.3DE1E1223EF@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).