From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw125177 [PATCH] net/iavf: fix dev stop return value
Date: Thu, 16 Mar 2023 04:59:26 -0400 [thread overview]
Message-ID: <20230316085926.1348848-1-robot@bytheb.org> (raw)
In-Reply-To: <20230316071449.532296-1-zhichaox.zeng@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/125177/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4434542679
next prev parent reply other threads:[~2023-03-16 7:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316071449.532296-1-zhichaox.zeng@intel.com>
2023-03-16 6:59 ` qemudev
2023-03-16 7:03 ` qemudev
2023-03-16 7:11 ` checkpatch
2023-03-16 8:59 ` 0-day Robot [this message]
2023-03-20 19:56 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-20 18:03 dpdklab
2023-03-18 8:51 dpdklab
2023-03-18 8:12 dpdklab
2023-03-16 15:53 dpdklab
2023-03-16 15:02 dpdklab
2023-03-16 11:43 dpdklab
2023-03-16 11:43 dpdklab
2023-03-16 10:49 dpdklab
2023-03-16 10:45 dpdklab
2023-03-16 10:24 dpdklab
2023-03-16 9:25 dpdklab
2023-03-16 8:58 dpdklab
2023-03-16 8:49 dpdklab
2023-03-16 8:48 dpdklab
2023-03-16 8:46 dpdklab
2023-03-16 8:45 dpdklab
2023-03-16 8:44 dpdklab
2023-03-16 8:41 dpdklab
2023-03-16 8:39 dpdklab
2023-03-16 8:36 dpdklab
2023-03-16 8:36 dpdklab
2023-03-16 8:29 dpdklab
2023-03-16 8:29 dpdklab
2023-03-16 8:26 dpdklab
2023-03-16 8:25 dpdklab
2023-03-16 8:25 dpdklab
2023-03-16 8:21 dpdklab
2023-03-16 8:20 dpdklab
2023-03-16 8:19 dpdklab
2023-03-16 8:16 dpdklab
2023-03-16 8:15 dpdklab
2023-03-16 8:09 dpdklab
2023-03-16 8:08 dpdklab
2023-03-16 8:05 dpdklab
2023-03-16 8: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=20230316085926.1348848-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).