From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138377 [PATCH v7 2/2] doc: announce Intel IPsec MB version bump
Date: Thu, 14 Mar 2024 11:38:11 +0100 (CET) [thread overview]
Message-ID: <20240314103811.795851223EF@dpdk.org> (raw)
In-Reply-To: <20240314103731.3242086-2-brian.dooley@intel.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138377
_coding style OK_
next prev parent reply other threads:[~2024-03-14 10:38 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314103731.3242086-2-brian.dooley@intel.com>
2024-03-14 10:15 ` |SUCCESS| pw138376-138377 " qemudev
2024-03-14 10:20 ` qemudev
2024-03-14 10:38 ` checkpatch [this message]
2024-03-14 11:23 ` |SUCCESS| pw138377 " 0-day Robot
2024-03-14 11:41 ` |SUCCESS| pw138376-138377 [PATCH] [v7,2/2] doc: announce Intel IPsec dpdklab
2024-03-14 11:44 ` dpdklab
2024-03-14 11:44 ` 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:48 ` dpdklab
2024-03-14 11:48 ` dpdklab
2024-03-14 11:49 ` dpdklab
2024-03-14 11:49 ` dpdklab
2024-03-14 11:50 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 11:55 ` dpdklab
2024-03-14 11:57 ` dpdklab
2024-03-14 12:08 ` dpdklab
2024-03-14 12:15 ` dpdklab
2024-03-14 12:17 ` dpdklab
2024-03-14 12:18 ` dpdklab
2024-03-14 12:18 ` dpdklab
2024-03-14 12:20 ` dpdklab
2024-03-14 12:27 ` dpdklab
2024-03-14 12:27 ` dpdklab
2024-03-14 12:27 ` dpdklab
2024-03-14 12:27 ` dpdklab
2024-03-14 12:28 ` dpdklab
2024-03-14 12:28 ` dpdklab
2024-03-14 12:28 ` dpdklab
2024-03-14 12:28 ` dpdklab
2024-03-14 12:28 ` dpdklab
2024-03-14 12:28 ` dpdklab
2024-03-14 12:28 ` dpdklab
2024-03-14 12:29 ` dpdklab
2024-03-14 12:29 ` dpdklab
2024-03-14 12:29 ` dpdklab
2024-03-14 12:29 ` dpdklab
2024-03-14 12:29 ` dpdklab
2024-03-14 12:30 ` dpdklab
2024-03-14 12:30 ` dpdklab
2024-03-14 12:30 ` dpdklab
2024-03-14 12:30 ` dpdklab
2024-03-14 12:30 ` dpdklab
2024-03-14 12:30 ` dpdklab
2024-03-14 12:34 ` dpdklab
2024-03-14 12:46 ` dpdklab
2024-03-14 12:46 ` dpdklab
2024-03-14 12:48 ` dpdklab
2024-03-14 12:49 ` dpdklab
2024-03-14 12:49 ` dpdklab
2024-03-14 12:50 ` dpdklab
2024-03-14 12:50 ` dpdklab
2024-03-14 12:51 ` dpdklab
2024-03-14 12:51 ` dpdklab
2024-03-14 12:52 ` dpdklab
2024-03-14 12:52 ` dpdklab
2024-03-14 12:53 ` dpdklab
2024-03-14 12:54 ` dpdklab
2024-03-14 12:54 ` dpdklab
2024-03-14 12:54 ` dpdklab
2024-03-14 12:55 ` dpdklab
2024-03-14 12:55 ` dpdklab
2024-03-14 12:55 ` dpdklab
2024-03-14 12:57 ` dpdklab
2024-03-14 13:01 ` dpdklab
2024-03-14 13:02 ` dpdklab
2024-03-14 13:03 ` dpdklab
2024-03-14 13:04 ` dpdklab
2024-03-14 13:28 ` dpdklab
2024-03-14 13:36 ` dpdklab
2024-03-14 13:37 ` dpdklab
2024-03-14 13:45 ` dpdklab
2024-03-18 5:14 ` dpdklab
2024-03-18 5:41 ` 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=20240314103811.795851223EF@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).