From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138438 [PATCH v2] windows: make getopt functions have const properties
Date: Sun, 17 Mar 2024 12:23:22 -0400 [thread overview]
Message-ID: <20240317162322.212522-1-robot@bytheb.org> (raw)
In-Reply-To: <20240317153413.5780-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138438/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8316555093
next prev parent reply other threads:[~2024-03-17 16:23 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240317153413.5780-1-stephen@networkplumber.org>
2024-03-17 15:15 ` qemudev
2024-03-17 15:20 ` qemudev
2024-03-17 15:34 ` |WARNING| " checkpatch
2024-03-17 16:17 ` |SUCCESS| pw138438 [PATCH] [v2] windows: make getopt functions have dpdklab
2024-03-17 16:18 ` dpdklab
2024-03-17 16:18 ` dpdklab
2024-03-17 16:18 ` dpdklab
2024-03-17 16:18 ` dpdklab
2024-03-17 16:18 ` dpdklab
2024-03-17 16:18 ` dpdklab
2024-03-17 16:19 ` dpdklab
2024-03-17 16:19 ` dpdklab
2024-03-17 16:19 ` dpdklab
2024-03-17 16:20 ` dpdklab
2024-03-17 16:20 ` dpdklab
2024-03-17 16:20 ` dpdklab
2024-03-17 16:20 ` dpdklab
2024-03-17 16:20 ` dpdklab
2024-03-17 16:20 ` dpdklab
2024-03-17 16:20 ` dpdklab
2024-03-17 16:21 ` dpdklab
2024-03-17 16:21 ` dpdklab
2024-03-17 16:21 ` dpdklab
2024-03-17 16:21 ` dpdklab
2024-03-17 16:22 ` dpdklab
2024-03-17 16:22 ` dpdklab
2024-03-17 16:22 ` dpdklab
2024-03-17 16:22 ` dpdklab
2024-03-17 16:22 ` dpdklab
2024-03-17 16:22 ` dpdklab
2024-03-17 16:22 ` dpdklab
2024-03-17 16:23 ` dpdklab
2024-03-17 16:23 ` dpdklab
2024-03-17 16:23 ` dpdklab
2024-03-17 16:23 ` 0-day Robot [this message]
2024-03-17 16:23 ` dpdklab
2024-03-17 16:23 ` dpdklab
2024-03-17 16:23 ` dpdklab
2024-03-17 16:23 ` dpdklab
2024-03-17 16:24 ` dpdklab
2024-03-17 16:24 ` dpdklab
2024-03-17 16:24 ` dpdklab
2024-03-17 16:24 ` dpdklab
2024-03-17 16:25 ` dpdklab
2024-03-17 16:25 ` dpdklab
2024-03-17 16:25 ` dpdklab
2024-03-17 16:25 ` dpdklab
2024-03-17 16:25 ` dpdklab
2024-03-17 16:26 ` dpdklab
2024-03-17 16:26 ` dpdklab
2024-03-17 16:27 ` dpdklab
2024-03-17 16:28 ` dpdklab
2024-03-17 16:28 ` dpdklab
2024-03-17 16:28 ` dpdklab
2024-03-17 16:29 ` dpdklab
2024-03-17 16:30 ` dpdklab
2024-03-17 16:30 ` dpdklab
2024-03-17 16:31 ` dpdklab
2024-03-17 16:31 ` dpdklab
2024-03-17 16:31 ` dpdklab
2024-03-17 16:34 ` dpdklab
2024-03-17 16:36 ` dpdklab
2024-03-17 16:37 ` dpdklab
2024-03-17 16:37 ` dpdklab
2024-03-17 16:38 ` dpdklab
2024-03-17 16:40 ` dpdklab
2024-03-17 16:42 ` dpdklab
2024-03-17 16:50 ` dpdklab
2024-03-17 17:20 ` dpdklab
2024-03-17 17:30 ` dpdklab
2024-03-20 1:23 ` dpdklab
2024-03-20 1:59 ` 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=20240317162322.212522-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).