From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw138579 [PATCH] net/ixgbe: do not update link status in secondary process
Date: Wed, 20 Mar 2024 18:38:58 +0100 (CET) [thread overview]
Message-ID: <20240320173858.0EF191223F9@dpdk.org> (raw)
In-Reply-To: <20240320173407.216307-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/138579
_coding style OK_
next prev parent reply other threads:[~2024-03-20 17:39 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320173407.216307-1-stephen@networkplumber.org>
2024-03-20 17:16 ` qemudev
2024-03-20 17:21 ` qemudev
2024-03-20 17:38 ` checkpatch [this message]
2024-03-20 18:24 ` |FAILURE| " 0-day Robot
2024-03-20 22:27 ` |SUCCESS| pw138579 [PATCH] net/ixgbe: do not update link status in s dpdklab
2024-03-20 22:36 ` dpdklab
2024-03-20 22:37 ` dpdklab
2024-03-20 22:48 ` dpdklab
2024-03-20 22:52 ` dpdklab
2024-03-20 22:55 ` dpdklab
2024-03-20 22:56 ` dpdklab
2024-03-20 23:00 ` dpdklab
2024-03-20 23:17 ` dpdklab
2024-03-20 23:18 ` dpdklab
2024-03-20 23:20 ` dpdklab
2024-03-20 23:21 ` dpdklab
2024-03-20 23:21 ` dpdklab
2024-03-20 23:23 ` dpdklab
2024-03-20 23:23 ` dpdklab
2024-03-20 23:24 ` dpdklab
2024-03-20 23:24 ` dpdklab
2024-03-20 23:24 ` dpdklab
2024-03-20 23:25 ` dpdklab
2024-03-20 23:25 ` dpdklab
2024-03-20 23:25 ` dpdklab
2024-03-20 23:26 ` dpdklab
2024-03-20 23:26 ` dpdklab
2024-03-20 23:26 ` dpdklab
2024-03-20 23:27 ` dpdklab
2024-03-20 23:28 ` dpdklab
2024-03-20 23:28 ` dpdklab
2024-03-20 23:28 ` dpdklab
2024-03-20 23:29 ` dpdklab
2024-03-20 23:30 ` dpdklab
2024-03-20 23:30 ` dpdklab
2024-03-20 23:31 ` dpdklab
2024-03-20 23:31 ` dpdklab
2024-03-20 23:32 ` dpdklab
2024-03-20 23:32 ` dpdklab
2024-03-20 23:32 ` dpdklab
2024-03-20 23:32 ` dpdklab
2024-03-20 23:33 ` dpdklab
2024-03-20 23:33 ` dpdklab
2024-03-20 23:34 ` dpdklab
2024-03-20 23:35 ` dpdklab
2024-03-20 23:36 ` dpdklab
2024-03-20 23:36 ` dpdklab
2024-03-20 23:37 ` dpdklab
2024-03-20 23:40 ` dpdklab
2024-03-20 23:40 ` dpdklab
2024-03-20 23:41 ` dpdklab
2024-03-20 23:41 ` dpdklab
2024-03-20 23:41 ` dpdklab
2024-03-20 23:42 ` dpdklab
2024-03-20 23:42 ` dpdklab
2024-03-20 23:42 ` dpdklab
2024-03-20 23:43 ` dpdklab
2024-03-20 23:52 ` dpdklab
2024-03-20 23:52 ` dpdklab
2024-03-20 23:52 ` dpdklab
2024-03-20 23:54 ` dpdklab
2024-03-20 23:54 ` dpdklab
2024-03-20 23:54 ` dpdklab
2024-03-20 23:55 ` dpdklab
2024-03-20 23:55 ` dpdklab
2024-03-20 23:56 ` dpdklab
2024-03-20 23:59 ` dpdklab
2024-03-20 23:59 ` dpdklab
2024-03-20 23:59 ` dpdklab
2024-03-21 0:00 ` dpdklab
2024-03-21 0:02 ` dpdklab
2024-03-21 0:16 ` dpdklab
2024-03-21 0:18 ` dpdklab
2024-03-21 0:18 ` dpdklab
2024-03-21 0:37 ` dpdklab
2024-03-21 0:45 ` dpdklab
2024-03-21 0:51 ` dpdklab
2024-03-21 1:45 ` dpdklab
2024-03-21 15:20 ` dpdklab
2024-03-22 11:47 ` dpdklab
2024-03-22 12:27 ` 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=20240320173858.0EF191223F9@dpdk.org \
--to=checkpatch@dpdk.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).