From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw138336 [PATCH] net/iavf: fix fail to reset vf when using dcf
Date: Wed, 13 Mar 2024 22:43:13 -0400 [thread overview]
Message-ID: <20240314024313.296721-1-robot@bytheb.org> (raw)
In-Reply-To: <20240314010049.340381-1-kaiwenx.deng@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/138336/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8274383949
next prev parent reply other threads:[~2024-03-14 2:43 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314010049.340381-1-kaiwenx.deng@intel.com>
2024-03-14 1:27 ` qemudev
2024-03-14 1:31 ` qemudev
2024-03-14 1:45 ` checkpatch
2024-03-14 2:19 ` |SUCCESS| pw138336 [PATCH] net/iavf: fix fail to reset vf when using dpdklab
2024-03-14 2:20 ` dpdklab
2024-03-14 2:20 ` dpdklab
2024-03-14 2:21 ` dpdklab
2024-03-14 2:23 ` dpdklab
2024-03-14 2:23 ` dpdklab
2024-03-14 2:24 ` dpdklab
2024-03-14 2:24 ` dpdklab
2024-03-14 2:24 ` dpdklab
2024-03-14 2:24 ` dpdklab
2024-03-14 2:25 ` dpdklab
2024-03-14 2:25 ` dpdklab
2024-03-14 2:25 ` dpdklab
2024-03-14 2:25 ` dpdklab
2024-03-14 2:26 ` dpdklab
2024-03-14 2:26 ` dpdklab
2024-03-14 2:26 ` dpdklab
2024-03-14 2:26 ` dpdklab
2024-03-14 2:27 ` dpdklab
2024-03-14 2:27 ` dpdklab
2024-03-14 2:27 ` dpdklab
2024-03-14 2:27 ` dpdklab
2024-03-14 2:27 ` dpdklab
2024-03-14 2:28 ` dpdklab
2024-03-14 2:28 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:29 ` dpdklab
2024-03-14 2:30 ` dpdklab
2024-03-14 2:30 ` dpdklab
2024-03-14 2:30 ` dpdklab
2024-03-14 2:30 ` dpdklab
2024-03-14 2:31 ` dpdklab
2024-03-14 2:34 ` dpdklab
2024-03-14 2:34 ` dpdklab
2024-03-14 2:35 ` dpdklab
2024-03-14 2:35 ` dpdklab
2024-03-14 2:37 ` dpdklab
2024-03-14 2:38 ` dpdklab
2024-03-14 2:38 ` dpdklab
2024-03-14 2:38 ` dpdklab
2024-03-14 2:38 ` dpdklab
2024-03-14 2:38 ` dpdklab
2024-03-14 2:39 ` dpdklab
2024-03-14 2:39 ` dpdklab
2024-03-14 2:39 ` dpdklab
2024-03-14 2:40 ` dpdklab
2024-03-14 2:40 ` dpdklab
2024-03-14 2:41 ` dpdklab
2024-03-14 2:43 ` 0-day Robot [this message]
2024-03-14 2:46 ` dpdklab
2024-03-14 2:52 ` dpdklab
2024-03-14 2:53 ` dpdklab
2024-03-14 2:53 ` dpdklab
2024-03-14 2:55 ` dpdklab
2024-03-14 2:55 ` dpdklab
2024-03-14 2:55 ` dpdklab
2024-03-14 2:55 ` dpdklab
2024-03-14 2:56 ` dpdklab
2024-03-14 2:56 ` dpdklab
2024-03-14 2:57 ` dpdklab
2024-03-14 2:58 ` dpdklab
2024-03-14 2:59 ` dpdklab
2024-03-14 3:21 ` dpdklab
2024-03-14 3:42 ` dpdklab
2024-03-17 14:43 ` dpdklab
2024-03-17 15:23 ` 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=20240314024313.296721-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).