From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw142406 [PATCH] doc: clarify mempool striding optimisation on Arm
Date: Mon, 15 Jul 2024 11:44:01 -0400 [thread overview]
Message-ID: <20240715154401.2881013-1-robot@bytheb.org> (raw)
In-Reply-To: <20240715144420.36292-1-jack.bond-preston@foss.arm.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/142406/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9941854049
next prev parent reply other threads:[~2024-07-15 15:44 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240715144420.36292-1-jack.bond-preston@foss.arm.com>
2024-07-15 14:17 ` qemudev
2024-07-15 14:22 ` qemudev
2024-07-15 14:45 ` checkpatch
2024-07-15 15:44 ` 0-day Robot [this message]
2024-07-15 20:57 ` |SUCCESS| pw142406 [PATCH] doc: clarify mempool striding optimisatio dpdklab
2024-07-15 21:01 ` dpdklab
2024-07-15 21:02 ` dpdklab
2024-07-15 21:05 ` dpdklab
2024-07-15 21:14 ` dpdklab
2024-07-15 21:19 ` dpdklab
2024-07-15 21:20 ` dpdklab
2024-07-15 21:45 ` dpdklab
2024-07-15 22:33 ` |PENDING| " dpdklab
2024-07-15 22:35 ` dpdklab
2024-07-15 22:41 ` |SUCCESS| " dpdklab
2024-07-15 22:41 ` |PENDING| " dpdklab
2024-07-15 22:44 ` dpdklab
2024-07-15 22:45 ` dpdklab
2024-07-15 22:45 ` dpdklab
2024-07-15 22:51 ` dpdklab
2024-07-15 22:55 ` |SUCCESS| " dpdklab
2024-07-15 22:56 ` dpdklab
2024-07-15 22:58 ` |PENDING| " dpdklab
2024-07-15 23:14 ` |SUCCESS| " dpdklab
2024-07-15 23:20 ` |PENDING| " dpdklab
2024-07-15 23:21 ` dpdklab
2024-07-15 23:23 ` dpdklab
2024-07-15 23:25 ` dpdklab
2024-07-15 23:27 ` dpdklab
2024-07-15 23:28 ` dpdklab
2024-07-15 23:30 ` dpdklab
2024-07-15 23:35 ` dpdklab
2024-07-15 23:41 ` dpdklab
2024-07-15 23:48 ` dpdklab
2024-07-15 23:50 ` dpdklab
2024-07-15 23:53 ` dpdklab
2024-07-15 23:56 ` dpdklab
2024-07-15 23:58 ` dpdklab
2024-07-16 0:00 ` dpdklab
2024-07-16 0:03 ` dpdklab
2024-07-16 0:50 ` dpdklab
2024-07-16 0:52 ` dpdklab
2024-07-16 0:55 ` dpdklab
2024-07-16 0:56 ` dpdklab
2024-07-16 0:58 ` dpdklab
2024-07-16 0:58 ` dpdklab
2024-07-16 0:59 ` dpdklab
2024-07-16 0:59 ` dpdklab
2024-07-16 0:59 ` dpdklab
2024-07-16 0:59 ` dpdklab
2024-07-16 1:04 ` dpdklab
2024-07-16 1:22 ` dpdklab
2024-07-16 1:24 ` dpdklab
2024-07-16 1:29 ` dpdklab
2024-07-16 1:34 ` dpdklab
2024-07-16 1:41 ` dpdklab
2024-07-16 1:48 ` dpdklab
2024-07-16 1:52 ` dpdklab
2024-07-16 1:54 ` dpdklab
2024-07-16 1:54 ` dpdklab
2024-07-16 1:56 ` dpdklab
2024-07-16 1:59 ` dpdklab
2024-07-16 1:59 ` dpdklab
2024-07-16 2:04 ` dpdklab
2024-07-16 2:08 ` |SUCCESS| " dpdklab
2024-07-16 2:18 ` |PENDING| " dpdklab
2024-07-16 2:19 ` dpdklab
2024-07-16 3:01 ` dpdklab
2024-07-16 3:03 ` dpdklab
2024-07-16 3:07 ` dpdklab
2024-07-16 3:08 ` |SUCCESS| " dpdklab
2024-07-16 3:11 ` |PENDING| " dpdklab
2024-07-16 3:15 ` dpdklab
2024-07-16 3:17 ` dpdklab
2024-07-16 3:19 ` dpdklab
2024-07-16 3:22 ` dpdklab
2024-07-16 3:23 ` dpdklab
2024-07-16 3:24 ` dpdklab
2024-07-16 3:27 ` dpdklab
2024-07-16 3:28 ` dpdklab
2024-07-16 3:30 ` dpdklab
2024-07-16 3:31 ` dpdklab
2024-07-16 3:36 ` dpdklab
2024-07-16 3:40 ` dpdklab
2024-07-16 3:40 ` dpdklab
2024-07-16 3:41 ` dpdklab
2024-07-16 3:41 ` dpdklab
2024-07-16 3:42 ` dpdklab
2024-07-16 3:44 ` dpdklab
2024-07-16 3:44 ` dpdklab
2024-07-16 3:44 ` dpdklab
2024-07-16 3:45 ` dpdklab
2024-07-16 3:45 ` |SUCCESS| " dpdklab
2024-07-16 3:45 ` |PENDING| " dpdklab
2024-07-16 3:46 ` |SUCCESS| " dpdklab
2024-07-16 3:46 ` dpdklab
2024-07-16 3:46 ` |PENDING| " dpdklab
2024-07-16 3:48 ` dpdklab
2024-07-16 3:55 ` dpdklab
2024-07-16 3:55 ` dpdklab
2024-07-16 3:58 ` dpdklab
2024-07-16 4:03 ` dpdklab
2024-07-16 4:09 ` dpdklab
2024-07-16 4:31 ` |SUCCESS| " dpdklab
2024-07-16 13:47 ` dpdklab
2024-07-16 16:21 ` dpdklab
2024-07-16 16:27 ` dpdklab
2024-07-16 16:35 ` dpdklab
2024-07-16 16:41 ` dpdklab
2024-07-16 17:01 ` 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=20240715154401.2881013-1-robot@bytheb.org \
--to=robot@bytheb.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).