From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138440 [PATCH v3 1/1] eal: add C++ include guard in generic/rte_vect.h
Date: Mon, 18 Mar 2024 03:44:40 +0100 (CET) [thread overview]
Message-ID: <20240318024441.083FB1223EF@dpdk.org> (raw)
In-Reply-To: <20240318024415.555614-1-ashish.sadanandan@gmail.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138440
_coding style OK_
next prev parent reply other threads:[~2024-03-18 2:44 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318024415.555614-1-ashish.sadanandan@gmail.com>
2024-03-18 2:24 ` qemudev
2024-03-18 2:29 ` qemudev
2024-03-18 2:44 ` checkpatch [this message]
2024-03-18 3:43 ` 0-day Robot
2024-03-18 9:23 ` |SUCCESS| pw138440 [PATCH] [v3,1/1] eal: add C++ include guard in ge dpdklab
2024-03-18 9:24 ` dpdklab
2024-03-18 9:25 ` dpdklab
2024-03-18 9:44 ` dpdklab
2024-03-18 9:44 ` dpdklab
2024-03-18 9:45 ` dpdklab
2024-03-18 9:45 ` dpdklab
2024-03-18 9:45 ` dpdklab
2024-03-18 9:46 ` dpdklab
2024-03-18 9:47 ` dpdklab
2024-03-18 9:49 ` dpdklab
2024-03-18 10:02 ` dpdklab
2024-03-18 10:03 ` dpdklab
2024-03-18 10:04 ` dpdklab
2024-03-18 10:06 ` dpdklab
2024-03-18 10:06 ` dpdklab
2024-03-18 10:06 ` dpdklab
2024-03-18 10:07 ` dpdklab
2024-03-18 10:07 ` dpdklab
2024-03-18 10:07 ` dpdklab
2024-03-18 10:08 ` dpdklab
2024-03-18 10:09 ` dpdklab
2024-03-18 10:10 ` dpdklab
2024-03-18 10:19 ` dpdklab
2024-03-18 10:20 ` dpdklab
2024-03-18 10:20 ` dpdklab
2024-03-18 10:21 ` dpdklab
2024-03-18 10:21 ` dpdklab
2024-03-18 10:22 ` dpdklab
2024-03-18 10:23 ` dpdklab
2024-03-18 10:23 ` dpdklab
2024-03-18 10:23 ` dpdklab
2024-03-18 10:24 ` dpdklab
2024-03-18 10:25 ` dpdklab
2024-03-18 10:25 ` dpdklab
2024-03-18 10:25 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:32 ` dpdklab
2024-03-18 10:32 ` dpdklab
2024-03-18 10:32 ` dpdklab
2024-03-18 10:47 ` dpdklab
2024-03-18 10:47 ` dpdklab
2024-03-18 10:48 ` dpdklab
2024-03-18 10:48 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:57 ` dpdklab
2024-03-18 11:08 ` dpdklab
2024-03-18 11:11 ` dpdklab
2024-03-18 11:12 ` dpdklab
2024-03-18 11:17 ` dpdklab
2024-03-18 12:40 ` dpdklab
2024-03-18 12:43 ` dpdklab
2024-03-18 12:46 ` dpdklab
2024-03-20 10:40 ` dpdklab
2024-03-20 11:16 ` 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=20240318024441.083FB1223EF@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).