From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw137457 [PATCH] net/mlx5: fix counter cache starvation
Date: Wed, 28 Feb 2024 15:05:00 -0500 [thread overview]
Message-ID: <20240228200500.794935-1-robot@bytheb.org> (raw)
In-Reply-To: <20240228190607.187958-1-dsosnowski@nvidia.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/137457/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8085986454
next prev parent reply other threads:[~2024-02-28 20:05 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228190607.187958-1-dsosnowski@nvidia.com>
2024-02-28 18:44 ` qemudev
2024-02-28 18:48 ` qemudev
2024-02-28 19:08 ` checkpatch
2024-02-28 20:05 ` 0-day Robot [this message]
2024-02-29 1:44 ` dpdklab
2024-02-29 1:49 ` dpdklab
2024-02-29 1:50 ` dpdklab
2024-02-29 1:51 ` dpdklab
2024-02-29 1:51 ` dpdklab
2024-02-29 1:52 ` dpdklab
2024-02-29 1:53 ` dpdklab
2024-02-29 1:54 ` dpdklab
2024-02-29 1:54 ` dpdklab
2024-02-29 1:54 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:55 ` dpdklab
2024-02-29 1:56 ` dpdklab
2024-02-29 1:58 ` dpdklab
2024-02-29 1:58 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 1:59 ` dpdklab
2024-02-29 2:00 ` dpdklab
2024-02-29 2:00 ` dpdklab
2024-02-29 2:01 ` dpdklab
2024-02-29 2:01 ` dpdklab
2024-02-29 2:01 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:02 ` dpdklab
2024-02-29 2:03 ` dpdklab
2024-02-29 2:03 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:04 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:05 ` dpdklab
2024-02-29 2:06 ` dpdklab
2024-02-29 2:06 ` dpdklab
2024-02-29 2:11 ` dpdklab
2024-02-29 2:15 ` dpdklab
2024-02-29 2:15 ` dpdklab
2024-02-29 2:15 ` dpdklab
2024-02-29 2:18 ` dpdklab
2024-02-29 2:19 ` dpdklab
2024-02-29 2:19 ` dpdklab
2024-02-29 2:20 ` dpdklab
2024-02-29 2:20 ` dpdklab
2024-02-29 2:20 ` dpdklab
2024-02-29 2:21 ` dpdklab
2024-02-29 2:22 ` dpdklab
2024-02-29 2:22 ` dpdklab
2024-02-29 2:22 ` dpdklab
2024-02-29 2:24 ` dpdklab
2024-02-29 2:24 ` dpdklab
2024-02-29 3:05 ` dpdklab
2024-03-01 1:51 ` dpdklab
2024-03-01 1:57 ` dpdklab
2024-03-01 2:08 ` dpdklab
2024-03-01 2:08 ` dpdklab
2024-03-01 16:50 ` |WARNING| " dpdklab
2024-03-02 8:35 ` |SUCCESS| " dpdklab
2024-03-02 9:08 ` dpdklab
2024-03-02 9:40 ` |WARNING| " dpdklab
2024-03-02 21:50 ` |SUCCESS| " 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=20240228200500.794935-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).