From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw143677 [PATCH] eal: increase max file descriptor for secondary process device
Date: Thu, 5 Sep 2024 13:24:32 -0400 [thread overview]
Message-ID: <20240905172432.724710-1-robot@bytheb.org> (raw)
In-Reply-To: <20240905162018.74301-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/143677/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/10724625078
next prev parent reply other threads:[~2024-09-05 17:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905162018.74301-1-stephen@networkplumber.org>
2024-09-05 15:53 ` qemudev
2024-09-05 15:58 ` qemudev
2024-09-05 16:21 ` checkpatch
2024-09-05 17:24 ` 0-day Robot [this message]
2024-09-05 23:38 ` |SUCCESS| pw143677 [PATCH] eal: increase max file descriptor for sec dpdklab
2024-09-05 23:53 ` dpdklab
2024-09-06 0:06 ` dpdklab
2024-09-06 0:14 ` dpdklab
2024-09-06 0:16 ` |PENDING| " dpdklab
2024-09-06 0:16 ` |SUCCESS| " dpdklab
2024-09-06 0:19 ` |PENDING| " dpdklab
2024-09-06 0:37 ` |SUCCESS| " dpdklab
2024-09-06 0:44 ` dpdklab
2024-09-06 1:10 ` |PENDING| " dpdklab
2024-09-06 1:57 ` dpdklab
2024-09-06 1:58 ` |SUCCESS| " dpdklab
2024-09-06 4:07 ` dpdklab
2024-09-06 6:18 ` dpdklab
2024-09-06 6:58 ` dpdklab
2024-09-06 6:58 ` dpdklab
2024-09-06 6:58 ` dpdklab
2024-09-06 7:02 ` dpdklab
2024-09-06 7:06 ` dpdklab
2024-09-06 7:08 ` dpdklab
2024-09-06 7:15 ` dpdklab
2024-09-06 7:48 ` dpdklab
2024-09-06 8:47 ` dpdklab
2024-09-06 9:15 ` dpdklab
2024-09-06 11:34 ` dpdklab
2024-09-06 11:38 ` dpdklab
2024-09-06 13:42 ` dpdklab
2024-09-07 17:26 ` dpdklab
2024-09-07 17:58 ` dpdklab
2024-09-17 18:00 ` dpdklab
2024-09-17 18:12 ` dpdklab
2024-09-17 18:30 ` dpdklab
2024-09-17 19: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=20240905172432.724710-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).