From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw125856 [PATCH v3] eventdev/eth_rx: fix invalid memory access
Date: Fri, 7 Apr 2023 03:58:50 -0400 [thread overview]
Message-ID: <20230407075850.1869128-1-robot@bytheb.org> (raw)
In-Reply-To: <20230407064732.891-1-pbhagavatula@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/125856/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4636184400
next prev parent reply other threads:[~2023-04-07 7:58 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230407064732.891-1-pbhagavatula@marvell.com>
2023-04-07 6:37 ` qemudev
2023-04-07 6:41 ` qemudev
2023-04-07 6:49 ` checkpatch
2023-04-07 7:58 ` 0-day Robot [this message]
2023-04-07 17:10 |SUCCESS| pw125856 [PATCH] [v3] " dpdklab
2023-04-07 17:14 dpdklab
2023-04-07 17:15 dpdklab
2023-04-07 17:15 dpdklab
2023-04-07 17:17 dpdklab
2023-04-07 17:17 dpdklab
2023-04-07 17:19 dpdklab
2023-04-07 17:20 dpdklab
2023-04-07 17:22 dpdklab
2023-04-07 17:23 dpdklab
2023-04-07 17:27 dpdklab
2023-04-07 17:32 dpdklab
2023-04-07 17:35 dpdklab
2023-04-07 18:03 dpdklab
2023-04-07 18:08 dpdklab
2023-04-07 18:09 dpdklab
2023-04-07 18:10 dpdklab
2023-04-07 18:11 dpdklab
2023-04-07 18:12 dpdklab
2023-04-07 18:13 dpdklab
2023-04-07 18:15 dpdklab
2023-04-07 18:18 dpdklab
2023-04-07 18:20 dpdklab
2023-04-07 18:25 dpdklab
2023-04-07 18:29 dpdklab
2023-04-07 18:35 dpdklab
2023-04-07 18:37 dpdklab
2023-04-07 18:42 dpdklab
2023-04-07 18:46 dpdklab
2023-04-07 18:46 dpdklab
2023-04-07 19:02 dpdklab
2023-04-07 19:05 dpdklab
2023-04-07 19:09 dpdklab
2023-04-07 19:12 dpdklab
2023-04-07 19:16 dpdklab
2023-04-07 19:20 dpdklab
2023-04-07 19:25 dpdklab
2023-04-07 19:28 dpdklab
2023-04-07 19:30 dpdklab
2023-04-07 19:39 dpdklab
2023-04-07 19:42 dpdklab
2023-04-07 19:47 dpdklab
2023-04-07 19:49 dpdklab
2023-04-07 19:55 dpdklab
2023-04-07 19:56 dpdklab
2023-04-07 20:09 dpdklab
2023-04-07 20:37 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=20230407075850.1869128-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).