From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138575 [PATCH] buildtools: fix build with clang 17
Date: Wed, 20 Mar 2024 17:01:53 +0100 (CET) [thread overview]
Message-ID: <20240320160153.B23101223F9@dpdk.org> (raw)
In-Reply-To: <20240320155814.617220-1-alialnu@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138575
_coding style OK_
next prev parent reply other threads:[~2024-03-20 16:05 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320155814.617220-1-alialnu@nvidia.com>
2024-03-20 15:37 ` qemudev
2024-03-20 15:42 ` qemudev
2024-03-20 16:01 ` checkpatch [this message]
2024-03-20 16:47 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:54 ` dpdklab
2024-03-20 16:54 ` dpdklab
2024-03-20 16:57 ` dpdklab
2024-03-20 16:57 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:59 ` |FAILURE| " dpdklab
2024-03-20 16:59 ` |SUCCESS| " dpdklab
2024-03-20 16:59 ` |FAILURE| " dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 16:59 ` |SUCCESS| " dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 17:01 ` dpdklab
2024-03-20 17:01 ` |FAILURE| " dpdklab
2024-03-20 17:01 ` |SUCCESS| " dpdklab
2024-03-20 17:01 ` |FAILURE| " dpdklab
2024-03-20 17:01 ` |SUCCESS| " dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:04 ` |FAILURE| " dpdklab
2024-03-20 17:04 ` dpdklab
2024-03-20 17:05 ` 0-day Robot
2024-03-20 17:05 ` |SUCCESS| " dpdklab
2024-03-20 17:05 ` |FAILURE| " dpdklab
2024-03-20 17:06 ` |SUCCESS| " dpdklab
2024-03-20 17:06 ` dpdklab
2024-03-20 17:20 ` |FAILURE| " dpdklab
2024-03-20 17:21 ` |SUCCESS| " dpdklab
2024-03-20 17:25 ` |FAILURE| " dpdklab
2024-03-20 17:29 ` |SUCCESS| " dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-21 11:37 ` dpdklab
2024-03-22 4:22 ` dpdklab
2024-03-22 5:02 ` 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=20240320160153.B23101223F9@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).