From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw154796 [PATCH v7 8/8] lib/pmu: fix out-of-bound access
Date: Fri, 27 Jun 2025 13:23:29 -0400 [thread overview]
Message-ID: <20250627172329.4095827-1-robot@bytheb.org> (raw)
In-Reply-To: <20250627154107.3405768-9-tduszynski@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/154796/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15930707958
next prev parent reply other threads:[~2025-06-27 17:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250627154107.3405768-9-tduszynski@marvell.com>
2025-06-27 15:07 ` |SUCCESS| pw154789-154796 " qemudev
2025-06-27 15:12 ` qemudev
2025-06-27 15:42 ` |SUCCESS| pw154796 " checkpatch
2025-06-27 17:23 ` 0-day Robot [this message]
2025-06-27 17:41 ` |SUCCESS| pw154789-154796 [PATCH] [v7,8/8] lib/pmu: fix out-of-bound dpdklab
2025-06-27 18:04 ` dpdklab
2025-06-27 19:10 ` dpdklab
2025-06-27 19:11 ` |PENDING| " dpdklab
2025-06-27 19:25 ` |SUCCESS| " dpdklab
2025-06-27 20:00 ` dpdklab
2025-06-27 20:39 ` |PENDING| " dpdklab
2025-06-27 21:31 ` |SUCCESS| " dpdklab
2025-06-27 22:08 ` dpdklab
2025-06-27 22:22 ` dpdklab
2025-06-27 22:57 ` dpdklab
2025-06-27 22:57 ` dpdklab
2025-06-27 22:58 ` dpdklab
2025-06-27 23:09 ` |WARNING| " dpdklab
2025-06-27 23:10 ` dpdklab
2025-06-27 23:10 ` dpdklab
2025-06-27 23:10 ` dpdklab
2025-06-27 23:11 ` dpdklab
2025-06-27 23:11 ` dpdklab
2025-06-27 23:11 ` dpdklab
2025-06-27 23:12 ` dpdklab
2025-06-27 23:12 ` dpdklab
2025-06-27 23:12 ` dpdklab
2025-06-27 23:12 ` 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=20250627172329.4095827-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).