From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143076 [RFC PATCH] config: make queues per port a meson config option
Date: Mon, 12 Aug 2024 10:42:32 -0400 [thread overview]
Message-ID: <20240812144232.853558-1-robot@bytheb.org> (raw)
In-Reply-To: <20240812132910.162252-1-bruce.richardson@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143076/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10353125151
next prev parent reply other threads:[~2024-08-12 14:42 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240812132910.162252-1-bruce.richardson@intel.com>
2024-08-12 13:07 ` qemudev
2024-08-12 13:11 ` qemudev
2024-08-12 13:30 ` checkpatch
2024-08-12 14:42 ` 0-day Robot [this message]
2024-08-12 20:37 ` |SUCCESS| pw143076 [PATCH] [RFC] config: make queues per port a meso dpdklab
2024-08-12 21:39 ` |PENDING| " dpdklab
2024-08-12 21:52 ` |SUCCESS| " dpdklab
2024-08-12 22:05 ` |PENDING| " dpdklab
2024-08-12 22:14 ` |SUCCESS| " dpdklab
2024-08-12 22:19 ` dpdklab
2024-08-12 22:23 ` dpdklab
2024-08-12 22:37 ` dpdklab
2024-08-12 23:04 ` dpdklab
2024-08-13 0:39 ` |PENDING| " dpdklab
2024-08-13 0:48 ` |SUCCESS| " dpdklab
2024-08-13 1:20 ` |PENDING| " dpdklab
2024-08-13 1:20 ` dpdklab
2024-08-13 1:21 ` dpdklab
2024-08-13 1:22 ` dpdklab
2024-08-13 1:22 ` |SUCCESS| " dpdklab
2024-08-13 1:26 ` |PENDING| " dpdklab
2024-08-13 1:28 ` dpdklab
2024-08-13 1:31 ` dpdklab
2024-08-13 1:32 ` dpdklab
2024-08-13 1:33 ` dpdklab
2024-08-13 1:33 ` dpdklab
2024-08-13 1:33 ` |SUCCESS| " dpdklab
2024-08-13 1:34 ` |PENDING| " dpdklab
2024-08-13 1:34 ` dpdklab
2024-08-13 1:35 ` dpdklab
2024-08-13 1:37 ` dpdklab
2024-08-13 1:37 ` dpdklab
2024-08-13 1:38 ` dpdklab
2024-08-13 1:40 ` dpdklab
2024-08-13 1:44 ` dpdklab
2024-08-13 1:44 ` dpdklab
2024-08-13 1:45 ` dpdklab
2024-08-13 1:45 ` dpdklab
2024-08-13 1:46 ` dpdklab
2024-08-13 1:46 ` dpdklab
2024-08-13 1:47 ` dpdklab
2024-08-13 1:47 ` dpdklab
2024-08-13 1:48 ` dpdklab
2024-08-13 1:50 ` dpdklab
2024-08-13 1:51 ` dpdklab
2024-08-13 1:52 ` |SUCCESS| " dpdklab
2024-08-13 1:52 ` dpdklab
2024-08-13 1:53 ` dpdklab
2024-08-13 1:55 ` |PENDING| " dpdklab
2024-08-13 1:56 ` dpdklab
2024-08-13 1:58 ` dpdklab
2024-08-13 1:58 ` dpdklab
2024-08-13 2:01 ` dpdklab
2024-08-13 2:02 ` dpdklab
2024-08-13 2:03 ` dpdklab
2024-08-13 2:05 ` dpdklab
2024-08-13 2:06 ` dpdklab
2024-08-13 2:06 ` dpdklab
2024-08-13 2:07 ` dpdklab
2024-08-13 2:07 ` dpdklab
2024-08-13 2:07 ` dpdklab
2024-08-13 2:08 ` |SUCCESS| " dpdklab
2024-08-13 2:09 ` |PENDING| " dpdklab
2024-08-13 2:09 ` dpdklab
2024-08-13 2:11 ` dpdklab
2024-08-13 2:12 ` dpdklab
2024-08-13 2:12 ` dpdklab
2024-08-13 2:13 ` dpdklab
2024-08-13 2:14 ` dpdklab
2024-08-13 2:14 ` dpdklab
2024-08-13 2:14 ` dpdklab
2024-08-13 2:15 ` dpdklab
2024-08-13 2:16 ` dpdklab
2024-08-13 2:16 ` dpdklab
2024-08-13 2:18 ` dpdklab
2024-08-13 2:23 ` dpdklab
2024-08-13 2:23 ` dpdklab
2024-08-13 2:24 ` dpdklab
2024-08-13 2:24 ` dpdklab
2024-08-13 2:31 ` dpdklab
2024-08-13 2:31 ` dpdklab
2024-08-13 2:36 ` dpdklab
2024-08-13 2:42 ` dpdklab
2024-08-13 2:43 ` dpdklab
2024-08-13 2:44 ` dpdklab
2024-08-13 2:47 ` dpdklab
2024-08-13 2:51 ` dpdklab
2024-08-13 2:53 ` dpdklab
2024-08-13 2:55 ` |SUCCESS| " dpdklab
2024-08-13 3:00 ` |PENDING| " dpdklab
2024-08-13 3:02 ` |SUCCESS| " dpdklab
2024-08-13 3:04 ` |PENDING| " dpdklab
2024-08-13 3:07 ` |SUCCESS| " dpdklab
2024-08-13 3:07 ` |PENDING| " dpdklab
2024-08-13 3:08 ` dpdklab
2024-08-13 3:12 ` dpdklab
2024-08-13 3:18 ` |SUCCESS| " dpdklab
2024-08-13 3:25 ` dpdklab
2024-08-13 3:30 ` dpdklab
2024-08-13 4:22 ` 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=20240812144232.853558-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).