From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138250 [PATCH v2] windows: install sched.h header
Date: Tue, 12 Mar 2024 15:03:23 -0400 [thread overview]
Message-ID: <20240312190323.2938555-1-robot@bytheb.org> (raw)
In-Reply-To: <1710266077-26489-1-git-send-email-roretzla@linux.microsoft.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138250/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8253673011
next prev parent reply other threads:[~2024-03-12 19:03 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710266077-26489-1-git-send-email-roretzla@linux.microsoft.com>
2024-03-12 17:39 ` qemudev
2024-03-12 17:43 ` qemudev
2024-03-12 17:56 ` checkpatch
2024-03-12 19:03 ` 0-day Robot [this message]
2024-03-12 19:38 ` |SUCCESS| pw138250 [PATCH] [v2] " dpdklab
2024-03-12 19:38 ` dpdklab
2024-03-12 19:43 ` dpdklab
2024-03-12 19:43 ` dpdklab
2024-03-12 19:44 ` dpdklab
2024-03-12 19:47 ` dpdklab
2024-03-12 19:47 ` dpdklab
2024-03-12 19:48 ` dpdklab
2024-03-12 19:52 ` dpdklab
2024-03-12 19:52 ` dpdklab
2024-03-12 19:53 ` dpdklab
2024-03-12 19:53 ` dpdklab
2024-03-12 19:54 ` dpdklab
2024-03-12 19:54 ` dpdklab
2024-03-12 19:54 ` dpdklab
2024-03-12 19:55 ` dpdklab
2024-03-12 19:55 ` dpdklab
2024-03-12 20:15 ` dpdklab
2024-03-12 20:19 ` dpdklab
2024-03-12 20:20 ` dpdklab
2024-03-12 20:21 ` dpdklab
2024-03-12 20:31 ` dpdklab
2024-03-12 20:32 ` dpdklab
2024-03-12 20:32 ` dpdklab
2024-03-12 20:32 ` dpdklab
2024-03-12 20:32 ` dpdklab
2024-03-12 20:33 ` dpdklab
2024-03-12 20:33 ` dpdklab
2024-03-12 20:35 ` dpdklab
2024-03-12 20:36 ` dpdklab
2024-03-12 20:36 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:37 ` dpdklab
2024-03-12 20:38 ` dpdklab
2024-03-12 20:39 ` dpdklab
2024-03-12 20:39 ` dpdklab
2024-03-12 20:39 ` dpdklab
2024-03-12 20:39 ` dpdklab
2024-03-12 20:39 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:41 ` dpdklab
2024-03-12 20:42 ` dpdklab
2024-03-12 20:50 ` dpdklab
2024-03-12 20:50 ` dpdklab
2024-03-12 20:51 ` dpdklab
2024-03-12 20:52 ` dpdklab
2024-03-12 20:52 ` dpdklab
2024-03-12 20:52 ` dpdklab
2024-03-12 20:53 ` dpdklab
2024-03-12 20:53 ` dpdklab
2024-03-12 20:54 ` dpdklab
2024-03-12 20:59 ` dpdklab
2024-03-12 20:59 ` dpdklab
2024-03-12 21:00 ` dpdklab
2024-03-12 21:03 ` dpdklab
2024-03-12 21:07 ` dpdklab
2024-03-12 21:07 ` dpdklab
2024-03-12 21:08 ` dpdklab
2024-03-12 21:08 ` dpdklab
2024-03-12 21:10 ` dpdklab
2024-03-12 21:10 ` dpdklab
2024-03-12 21:12 ` dpdklab
2024-03-12 21:53 ` dpdklab
2024-03-12 22:39 ` dpdklab
2024-03-16 7:27 ` dpdklab
2024-03-16 8:00 ` 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=20240312190323.2938555-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).