From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw144418 [RFC PATCH v7] mempool: fix mempool cache size
Date: Tue, 24 Sep 2024 15:03:38 -0400 [thread overview]
Message-ID: <20240924190338.848882-1-robot@bytheb.org> (raw)
In-Reply-To: <20240924181224.1562346-1-mb@smartsharesystems.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/144418/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11019711119
next prev parent reply other threads:[~2024-09-24 19:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240924181224.1562346-1-mb@smartsharesystems.com>
2024-09-24 17:45 ` qemudev
2024-09-24 17:50 ` qemudev
2024-09-24 18:13 ` checkpatch
2024-09-24 19:03 ` 0-day Robot [this message]
2024-09-25 8:35 ` |FAILURE| pw144418 [PATCH] [RFC,v7] " dpdklab
2024-09-25 8:44 ` |SUCCESS| " dpdklab
2024-09-25 8:46 ` dpdklab
2024-09-25 8:51 ` dpdklab
2024-09-25 8:57 ` dpdklab
2024-09-25 9:04 ` |FAILURE| " dpdklab
2024-09-25 9:09 ` |SUCCESS| " dpdklab
2024-09-25 9:10 ` dpdklab
2024-09-25 9:10 ` dpdklab
2024-09-25 9:16 ` dpdklab
2024-09-25 9:18 ` |FAILURE| " dpdklab
2024-09-25 9:21 ` |SUCCESS| " dpdklab
2024-09-25 9:24 ` dpdklab
2024-09-25 9:25 ` dpdklab
2024-09-25 9:33 ` dpdklab
2024-09-25 9:40 ` |FAILURE| " dpdklab
2024-09-25 9:50 ` |SUCCESS| " dpdklab
2024-09-25 9:58 ` dpdklab
2024-09-25 9:58 ` dpdklab
2024-09-25 10:10 ` dpdklab
2024-09-25 10:46 ` dpdklab
2024-09-25 10:52 ` |FAILURE| " dpdklab
2024-09-25 10:57 ` |PENDING| " dpdklab
2024-09-25 11:01 ` dpdklab
2024-09-25 11:18 ` dpdklab
2024-09-25 11:31 ` |SUCCESS| " dpdklab
2024-09-25 12:15 ` dpdklab
2024-09-25 12:47 ` |PENDING| " dpdklab
2024-09-25 12:49 ` |SUCCESS| " dpdklab
2024-09-25 13:20 ` dpdklab
2024-09-25 13:30 ` dpdklab
2024-09-25 16:23 ` 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=20240924190338.848882-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).