From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143593 [PATCH v1 1/1] usertools: add DPDK build directory setup script
Date: Wed, 4 Sep 2024 12:04:47 -0400 [thread overview]
Message-ID: <20240904160447.1825480-1-robot@bytheb.org> (raw)
In-Reply-To: <d961787cf29192bf329fec0cc0ac25e6397743f6.1725462616.git.anatoly.burakov@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143593/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10704789217
next prev parent reply other threads:[~2024-09-04 16:04 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d961787cf29192bf329fec0cc0ac25e6397743f6.1725462616.git.anatoly.burakov@intel.com>
2024-09-04 14:55 ` qemudev
2024-09-04 15:00 ` qemudev
2024-09-04 15:18 ` |WARNING| " checkpatch
2024-09-04 16:04 ` 0-day Robot [this message]
2024-09-04 21:56 ` |SUCCESS| pw143593 [PATCH] [v1,1/1] usertools: add DPDK build direct dpdklab
2024-09-04 22:03 ` dpdklab
2024-09-04 23:49 ` dpdklab
2024-09-04 23:50 ` dpdklab
2024-09-05 0:27 ` dpdklab
2024-09-05 0:33 ` dpdklab
2024-09-05 0:45 ` |PENDING| " dpdklab
2024-09-05 0:45 ` |SUCCESS| " dpdklab
2024-09-05 0:49 ` |PENDING| " dpdklab
2024-09-05 0:57 ` |SUCCESS| " dpdklab
2024-09-05 0:57 ` |PENDING| " dpdklab
2024-09-05 1:01 ` |SUCCESS| " dpdklab
2024-09-05 1:08 ` dpdklab
2024-09-05 1:10 ` dpdklab
2024-09-05 2:19 ` dpdklab
2024-09-05 2:20 ` dpdklab
2024-09-05 2:21 ` dpdklab
2024-09-05 2:27 ` dpdklab
2024-09-05 2:36 ` dpdklab
2024-09-05 2:45 ` dpdklab
2024-09-05 2:47 ` dpdklab
2024-09-05 2:55 ` dpdklab
2024-09-05 2:57 ` dpdklab
2024-09-05 2:59 ` dpdklab
2024-09-05 3:01 ` dpdklab
2024-09-05 3:02 ` dpdklab
2024-09-05 3:02 ` dpdklab
2024-09-05 3:03 ` dpdklab
2024-09-05 3:04 ` dpdklab
2024-09-05 3:04 ` dpdklab
2024-09-05 3:22 ` dpdklab
2024-09-05 3:30 ` dpdklab
2024-09-05 3:30 ` dpdklab
2024-09-05 3:33 ` dpdklab
2024-09-05 3:34 ` dpdklab
2024-09-05 3:34 ` dpdklab
2024-09-05 3:36 ` dpdklab
2024-09-05 3:37 ` dpdklab
2024-09-05 3:37 ` dpdklab
2024-09-05 3:43 ` dpdklab
2024-09-05 3:43 ` dpdklab
2024-09-05 3:44 ` dpdklab
2024-09-05 3:45 ` dpdklab
2024-09-05 3:45 ` dpdklab
2024-09-05 3:48 ` dpdklab
2024-09-05 3:51 ` dpdklab
2024-09-05 4:22 ` dpdklab
2024-09-05 8:34 ` dpdklab
2024-09-05 9:14 ` dpdklab
2024-09-05 17:24 ` dpdklab
2024-09-05 19:45 ` dpdklab
2024-09-18 6:21 ` dpdklab
2024-09-18 6:40 ` dpdklab
2024-09-18 6:51 ` dpdklab
2024-09-18 7:11 ` 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=20240904160447.1825480-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).