From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138046 [PATCH v3 33/33] net/ena: upgrade driver version to 2.9.0
Date: Wed, 6 Mar 2024 08:24:52 -0500 [thread overview]
Message-ID: <20240306132452.1033783-1-robot@bytheb.org> (raw)
In-Reply-To: <20240306122445.4350-34-shaibran@amazon.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138046/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8172287227
next prev parent reply other threads:[~2024-03-06 13:24 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306122445.4350-34-shaibran@amazon.com>
2024-03-06 12:06 ` |SUCCESS| pw138014-138046 " qemudev
2024-03-06 12:11 ` qemudev
2024-03-06 12:31 ` |SUCCESS| pw138046 " checkpatch
2024-03-06 13:24 ` 0-day Robot [this message]
2024-03-06 14:02 ` |SUCCESS| pw138014-138046 [PATCH] [v3,33/33] net/ena: upgrade driver dpdklab
2024-03-06 14:03 ` dpdklab
2024-03-06 14:04 ` dpdklab
2024-03-06 14:09 ` dpdklab
2024-03-06 14:10 ` dpdklab
2024-03-06 14:10 ` dpdklab
2024-03-06 14:14 ` dpdklab
2024-03-06 14:16 ` dpdklab
2024-03-06 14:24 ` dpdklab
2024-03-06 14:24 ` dpdklab
2024-03-06 14:25 ` dpdklab
2024-03-06 14:30 ` dpdklab
2024-03-06 14:30 ` dpdklab
2024-03-06 14:32 ` dpdklab
2024-03-06 14:48 ` dpdklab
2024-03-06 14:52 ` dpdklab
2024-03-06 14:54 ` dpdklab
2024-03-06 14:54 ` dpdklab
2024-03-06 14:55 ` dpdklab
2024-03-06 15:04 ` dpdklab
2024-03-06 15:25 ` dpdklab
2024-03-06 15:33 ` dpdklab
2024-03-06 15:33 ` dpdklab
2024-03-06 15:34 ` dpdklab
2024-03-06 15:34 ` dpdklab
2024-03-06 15:34 ` dpdklab
2024-03-06 15:35 ` dpdklab
2024-03-06 15:35 ` dpdklab
2024-03-06 15:36 ` dpdklab
2024-03-06 15:37 ` dpdklab
2024-03-06 15:38 ` dpdklab
2024-03-06 15:39 ` dpdklab
2024-03-06 15:44 ` dpdklab
2024-03-06 15:45 ` dpdklab
2024-03-06 15:45 ` dpdklab
2024-03-06 15:47 ` dpdklab
2024-03-06 15:52 ` dpdklab
2024-03-06 15:52 ` dpdklab
2024-03-06 15:54 ` dpdklab
2024-03-06 15:54 ` dpdklab
2024-03-06 15:56 ` dpdklab
2024-03-06 16:11 ` dpdklab
2024-03-06 16:13 ` dpdklab
2024-03-06 16:13 ` dpdklab
2024-03-06 16:14 ` dpdklab
2024-03-06 16:16 ` dpdklab
2024-03-06 16:16 ` dpdklab
2024-03-06 16:16 ` dpdklab
2024-03-06 16:17 ` dpdklab
2024-03-06 16:19 ` dpdklab
2024-03-06 16:20 ` dpdklab
2024-03-06 16:21 ` dpdklab
2024-03-06 16:23 ` dpdklab
2024-03-06 16:27 ` dpdklab
2024-03-06 16:28 ` dpdklab
2024-03-06 16:31 ` dpdklab
2024-03-06 16:31 ` dpdklab
2024-03-06 16:31 ` dpdklab
2024-03-06 16:32 ` dpdklab
2024-03-06 16:40 ` dpdklab
2024-03-06 16:41 ` dpdklab
2024-03-06 16:49 ` dpdklab
2024-03-06 17:39 ` dpdklab
2024-03-06 17:43 ` dpdklab
2024-03-06 19:18 ` dpdklab
2024-03-06 22:03 ` 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=20240306132452.1033783-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).