From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138177 [PATCH v2] doc: update size parameter details
Date: Tue, 12 Mar 2024 01:22:32 -0400 [thread overview]
Message-ID: <20240312052232.1343584-1-robot@bytheb.org> (raw)
In-Reply-To: <20240312042201.157-1-vipin.varghese@amd.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138177/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8243692510
next prev parent reply other threads:[~2024-03-12 5:22 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312042201.157-1-vipin.varghese@amd.com>
2024-03-12 3:58 ` qemudev
2024-03-12 4:03 ` qemudev
2024-03-12 4:23 ` checkpatch
2024-03-12 5:22 ` 0-day Robot [this message]
2024-03-12 5:50 ` |SUCCESS| pw138177 [PATCH] [v2] " dpdklab
2024-03-12 5:51 ` dpdklab
2024-03-12 5:51 ` dpdklab
2024-03-12 5:52 ` dpdklab
2024-03-12 5:53 ` dpdklab
2024-03-12 5:54 ` dpdklab
2024-03-12 5:54 ` dpdklab
2024-03-12 5:54 ` dpdklab
2024-03-12 5:55 ` dpdklab
2024-03-12 5:55 ` dpdklab
2024-03-12 5:56 ` dpdklab
2024-03-12 5:56 ` dpdklab
2024-03-12 5:57 ` dpdklab
2024-03-12 6:01 ` dpdklab
2024-03-12 6:02 ` dpdklab
2024-03-12 6:02 ` dpdklab
2024-03-12 6:03 ` dpdklab
2024-03-12 6:03 ` dpdklab
2024-03-12 6:03 ` dpdklab
2024-03-12 6:04 ` dpdklab
2024-03-12 6:06 ` dpdklab
2024-03-12 6:09 ` dpdklab
2024-03-12 6:09 ` dpdklab
2024-03-12 6:10 ` dpdklab
2024-03-12 6:10 ` dpdklab
2024-03-12 6:11 ` dpdklab
2024-03-12 6:13 ` dpdklab
2024-03-12 6:13 ` dpdklab
2024-03-12 6:13 ` dpdklab
2024-03-12 6:16 ` dpdklab
2024-03-12 6:16 ` dpdklab
2024-03-12 6:17 ` dpdklab
2024-03-12 6:17 ` dpdklab
2024-03-12 6:18 ` dpdklab
2024-03-12 6:18 ` dpdklab
2024-03-12 6:19 ` dpdklab
2024-03-12 6:19 ` dpdklab
2024-03-12 6:21 ` dpdklab
2024-03-12 6:21 ` dpdklab
2024-03-12 6:23 ` dpdklab
2024-03-12 6:24 ` dpdklab
2024-03-12 6:25 ` dpdklab
2024-03-12 6:31 ` dpdklab
2024-03-12 6:31 ` dpdklab
2024-03-12 6:32 ` dpdklab
2024-03-12 6:32 ` dpdklab
2024-03-12 6:32 ` dpdklab
2024-03-12 6:34 ` dpdklab
2024-03-12 6:35 ` dpdklab
2024-03-12 6:44 ` dpdklab
2024-03-12 6:44 ` dpdklab
2024-03-12 6:45 ` dpdklab
2024-03-12 6:51 ` dpdklab
2024-03-12 6:52 ` |FAILURE| " dpdklab
2024-03-12 6:53 ` dpdklab
2024-03-12 6:53 ` dpdklab
2024-03-12 6:54 ` dpdklab
2024-03-12 6:55 ` dpdklab
2024-03-12 6:55 ` dpdklab
2024-03-12 6:57 ` dpdklab
2024-03-12 6:58 ` dpdklab
2024-03-12 6:58 ` dpdklab
2024-03-12 7:00 ` dpdklab
2024-03-12 7:17 ` |SUCCESS| " dpdklab
2024-03-12 8:17 ` dpdklab
2024-03-12 8:23 ` dpdklab
2024-03-12 8:25 ` dpdklab
2024-03-12 9:40 ` dpdklab
2024-03-15 15:08 ` dpdklab
2024-03-15 15:31 ` 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=20240312052232.1343584-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).