From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138143 [RFC v2] eal: reduce size of internal config structure
Date: Sun, 10 Mar 2024 16:02:56 -0400 [thread overview]
Message-ID: <20240310200256.737012-1-robot@bytheb.org> (raw)
In-Reply-To: <20240310190759.305837-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138143/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8224260614
next prev parent reply other threads:[~2024-03-10 20:03 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240310190759.305837-1-stephen@networkplumber.org>
2024-03-10 18:45 ` qemudev
2024-03-10 18:49 ` qemudev
2024-03-10 19:08 ` checkpatch
2024-03-10 19:44 ` |SUCCESS| pw138143 [PATCH] [RFC,v2] eal: reduce size of internal con dpdklab
2024-03-10 19:45 ` dpdklab
2024-03-10 19:46 ` dpdklab
2024-03-10 19:46 ` dpdklab
2024-03-10 19:46 ` dpdklab
2024-03-10 19:47 ` dpdklab
2024-03-10 19:47 ` dpdklab
2024-03-10 19:48 ` dpdklab
2024-03-10 19:49 ` dpdklab
2024-03-10 19:50 ` dpdklab
2024-03-10 19:50 ` dpdklab
2024-03-10 19:51 ` dpdklab
2024-03-10 19:51 ` dpdklab
2024-03-10 19:51 ` dpdklab
2024-03-10 19:52 ` dpdklab
2024-03-10 19:52 ` dpdklab
2024-03-10 19:52 ` dpdklab
2024-03-10 19:53 ` dpdklab
2024-03-10 19:53 ` dpdklab
2024-03-10 19:53 ` dpdklab
2024-03-10 19:54 ` dpdklab
2024-03-10 19:54 ` dpdklab
2024-03-10 19:55 ` dpdklab
2024-03-10 19:55 ` dpdklab
2024-03-10 19:55 ` dpdklab
2024-03-10 19:55 ` dpdklab
2024-03-10 19:55 ` dpdklab
2024-03-10 19:56 ` dpdklab
2024-03-10 19:57 ` dpdklab
2024-03-10 19:57 ` dpdklab
2024-03-10 19:57 ` dpdklab
2024-03-10 19:57 ` dpdklab
2024-03-10 19:58 ` dpdklab
2024-03-10 19:59 ` dpdklab
2024-03-10 19:59 ` dpdklab
2024-03-10 19:59 ` dpdklab
2024-03-10 20:00 ` dpdklab
2024-03-10 20:00 ` dpdklab
2024-03-10 20:01 ` dpdklab
2024-03-10 20:02 ` dpdklab
2024-03-10 20:02 ` dpdklab
2024-03-10 20:02 ` 0-day Robot [this message]
2024-03-10 20:03 ` dpdklab
2024-03-10 20:04 ` dpdklab
2024-03-10 20:04 ` dpdklab
2024-03-10 20:06 ` dpdklab
2024-03-10 20:06 ` dpdklab
2024-03-10 20:07 ` dpdklab
2024-03-10 20:07 ` dpdklab
2024-03-10 20:09 ` dpdklab
2024-03-10 20:09 ` dpdklab
2024-03-10 20:11 ` dpdklab
2024-03-10 20:14 ` dpdklab
2024-03-10 20:14 ` dpdklab
2024-03-10 20:18 ` dpdklab
2024-03-10 20:18 ` dpdklab
2024-03-10 20:19 ` dpdklab
2024-03-10 20:21 ` dpdklab
2024-03-10 20:22 ` dpdklab
2024-03-10 20:24 ` dpdklab
2024-03-10 20:46 ` dpdklab
2024-03-10 20:52 ` dpdklab
2024-03-10 20:54 ` dpdklab
2024-03-10 21:00 ` dpdklab
2024-03-10 21:05 ` dpdklab
2024-03-10 21:11 ` dpdklab
2024-03-10 21:55 ` dpdklab
2024-03-10 22:06 ` dpdklab
2024-03-14 10:12 ` dpdklab
2024-03-14 10: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=20240310200256.737012-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).