From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw124838 [PATCH] eal: use program_invocation_short_name
Date: Tue, 7 Mar 2023 13:59:20 -0500 [thread overview]
Message-ID: <20230307185920.787567-1-robot@bytheb.org> (raw)
In-Reply-To: <20230307165319.68767-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/124838/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4356601558
next prev parent reply other threads:[~2023-03-07 17:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230307165319.68767-1-stephen@networkplumber.org>
2023-03-07 16:43 ` qemudev
2023-03-07 16:47 ` qemudev
2023-03-07 16:54 ` checkpatch
2023-03-07 18:59 ` 0-day Robot [this message]
2023-03-07 22:13 dpdklab
2023-03-07 22:19 dpdklab
2023-03-07 22:22 dpdklab
2023-03-07 22:22 dpdklab
2023-03-07 22:25 dpdklab
2023-03-07 22:26 dpdklab
2023-03-07 22:27 dpdklab
2023-03-07 22:29 dpdklab
2023-03-07 22:31 dpdklab
2023-03-07 22:33 dpdklab
2023-03-07 22:39 dpdklab
2023-03-07 23:21 dpdklab
2023-03-07 23:33 dpdklab
2023-03-07 23:48 dpdklab
2023-03-07 23:58 dpdklab
2023-03-07 23:58 dpdklab
2023-03-07 23:59 dpdklab
2023-03-07 23:59 dpdklab
2023-03-08 0:01 dpdklab
2023-03-08 0:01 dpdklab
2023-03-08 0:01 dpdklab
2023-03-08 0:06 dpdklab
2023-03-08 0:06 dpdklab
2023-03-08 0:07 dpdklab
2023-03-08 0:09 dpdklab
2023-03-08 0:16 dpdklab
2023-03-08 0:26 dpdklab
2023-03-08 0:32 dpdklab
2023-03-08 0:39 dpdklab
2023-03-08 0:54 dpdklab
2023-03-08 0:54 dpdklab
2023-03-08 1:13 dpdklab
2023-03-08 1:17 dpdklab
2023-03-08 1:41 dpdklab
2023-03-08 1:54 dpdklab
2023-03-08 2:34 dpdklab
2023-03-08 2:35 dpdklab
2023-03-08 3:14 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=20230307185920.787567-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).