From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw141998 [PATCH] eal/common: fix inconsistent representation of PCI numbers
Date: Mon, 1 Jul 2024 17:05:15 -0400 [thread overview]
Message-ID: <20240701210515.1413792-1-robot@bytheb.org> (raw)
In-Reply-To: <20240701200117.6349-1-shperetz@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/141998/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9750619775
next prev parent reply other threads:[~2024-07-01 21:05 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701200117.6349-1-shperetz@nvidia.com>
2024-07-01 19:35 ` qemudev
2024-07-01 19:39 ` qemudev
2024-07-01 20:03 ` checkpatch
2024-07-01 21:05 ` 0-day Robot [this message]
2024-07-01 21:53 ` |SUCCESS| pw141998 [PATCH] eal/common: fix inconsistent representati dpdklab
2024-07-01 21:55 ` dpdklab
2024-07-01 22:13 ` dpdklab
2024-07-01 22:27 ` dpdklab
2024-07-01 22:36 ` dpdklab
2024-07-01 22:41 ` dpdklab
2024-07-01 22:46 ` |PENDING| " dpdklab
2024-07-01 22:46 ` dpdklab
2024-07-01 22:46 ` |SUCCESS| " dpdklab
2024-07-01 22:46 ` |PENDING| " dpdklab
2024-07-01 22:51 ` dpdklab
2024-07-01 22:52 ` dpdklab
2024-07-01 22:52 ` dpdklab
2024-07-01 22:52 ` dpdklab
2024-07-01 22:53 ` dpdklab
2024-07-01 22:53 ` dpdklab
2024-07-01 23:00 ` dpdklab
2024-07-01 23:01 ` dpdklab
2024-07-01 23:03 ` |SUCCESS| " dpdklab
2024-07-01 23:04 ` |PENDING| " dpdklab
2024-07-01 23:04 ` dpdklab
2024-07-01 23:05 ` dpdklab
2024-07-01 23:06 ` |SUCCESS| " dpdklab
2024-07-01 23:07 ` |PENDING| " dpdklab
2024-07-01 23:17 ` dpdklab
2024-07-01 23:21 ` dpdklab
2024-07-01 23:21 ` dpdklab
2024-07-01 23:22 ` dpdklab
2024-07-01 23:24 ` dpdklab
2024-07-01 23:30 ` dpdklab
2024-07-01 23:38 ` |SUCCESS| " dpdklab
2024-07-01 23:38 ` dpdklab
2024-07-01 23:39 ` |PENDING| " dpdklab
2024-07-02 0:03 ` dpdklab
2024-07-02 0:23 ` dpdklab
2024-07-02 0:35 ` dpdklab
2024-07-02 0:36 ` dpdklab
2024-07-02 0:42 ` dpdklab
2024-07-02 0:44 ` dpdklab
2024-07-02 0:46 ` dpdklab
2024-07-02 0:46 ` dpdklab
2024-07-02 0:50 ` dpdklab
2024-07-02 0:54 ` dpdklab
2024-07-02 0:54 ` dpdklab
2024-07-02 0:57 ` dpdklab
2024-07-02 1:01 ` dpdklab
2024-07-02 1:03 ` dpdklab
2024-07-02 1:03 ` dpdklab
2024-07-02 1:07 ` dpdklab
2024-07-02 1:09 ` dpdklab
2024-07-02 1:12 ` dpdklab
2024-07-02 1:14 ` dpdklab
2024-07-02 1:16 ` dpdklab
2024-07-02 1:20 ` dpdklab
2024-07-02 1:20 ` dpdklab
2024-07-02 1:24 ` dpdklab
2024-07-02 1:24 ` dpdklab
2024-07-02 1:25 ` dpdklab
2024-07-02 1:28 ` dpdklab
2024-07-02 1:29 ` dpdklab
2024-07-02 1:30 ` dpdklab
2024-07-02 1:31 ` dpdklab
2024-07-02 1:35 ` |SUCCESS| " dpdklab
2024-07-02 1:35 ` |PENDING| " dpdklab
2024-07-02 1:37 ` dpdklab
2024-07-02 1:37 ` dpdklab
2024-07-02 1:39 ` dpdklab
2024-07-02 1:40 ` dpdklab
2024-07-02 1:44 ` dpdklab
2024-07-02 1:44 ` dpdklab
2024-07-02 1:48 ` dpdklab
2024-07-02 1:53 ` dpdklab
2024-07-02 2:05 ` |SUCCESS| " dpdklab
2024-07-02 2:45 ` |PENDING| " dpdklab
2024-07-02 2:58 ` dpdklab
2024-07-02 3:00 ` dpdklab
2024-07-02 3:04 ` dpdklab
2024-07-02 3:07 ` dpdklab
2024-07-02 3:14 ` dpdklab
2024-07-02 3:14 ` dpdklab
2024-07-02 3:29 ` dpdklab
2024-07-02 3:43 ` dpdklab
2024-07-02 3:58 ` dpdklab
2024-07-02 4:13 ` dpdklab
2024-07-02 4:17 ` dpdklab
2024-07-02 4:27 ` dpdklab
2024-07-02 4:33 ` dpdklab
2024-07-02 4:34 ` dpdklab
2024-07-02 4:36 ` dpdklab
2024-07-02 4:40 ` dpdklab
2024-07-02 4:41 ` dpdklab
2024-07-02 4:44 ` dpdklab
2024-07-02 4:52 ` dpdklab
2024-07-02 4:58 ` dpdklab
2024-07-02 5:00 ` dpdklab
2024-07-02 5:01 ` |SUCCESS| " dpdklab
2024-07-02 5:27 ` |PENDING| " dpdklab
2024-07-02 5:36 ` dpdklab
2024-07-02 5:49 ` dpdklab
2024-07-02 5:56 ` dpdklab
2024-07-02 6:06 ` dpdklab
2024-07-02 6:07 ` dpdklab
2024-07-02 6:43 ` |SUCCESS| " dpdklab
2024-07-02 7:08 ` dpdklab
2024-07-02 15:13 ` dpdklab
2024-07-02 15:27 ` 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=20240701210515.1413792-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).