From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw155978 [RFC 47/47] drivers/raw: replace with TAILQ_FOREACH_SAFE
Date: Tue, 19 Aug 2025 01:37:21 +0200 (CEST) [thread overview]
Message-ID: <20250818233721.0B2EE125245@dpdk.org> (raw)
In-Reply-To: <20250818233102.180207-48-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/155978
_coding style OK_
next prev parent reply other threads:[~2025-08-18 23:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250818233102.180207-48-stephen@networkplumber.org>
2025-08-18 23:05 ` |SUCCESS| pw155932-155978 " qemudev
2025-08-18 23:10 ` qemudev
2025-08-18 23:37 ` checkpatch [this message]
2025-08-19 0:45 ` |FAILURE| pw155978 " 0-day Robot
2025-08-19 5:50 ` |FAILURE| pw155932-155978 [PATCH] [RFC,47/47] drivers/raw: replace w dpdklab
2025-08-19 5:52 ` |SUCCESS| " dpdklab
2025-08-19 5:57 ` |PENDING| " dpdklab
2025-08-19 6:02 ` |FAILURE| " dpdklab
2025-08-19 6:10 ` dpdklab
2025-08-19 6:15 ` |SUCCESS| " dpdklab
2025-08-19 6:18 ` dpdklab
2025-08-19 6:20 ` |PENDING| " dpdklab
2025-08-19 6:24 ` |FAILURE| " dpdklab
2025-08-19 6:35 ` |PENDING| " dpdklab
2025-08-19 6:38 ` |SUCCESS| " dpdklab
2025-08-19 6:39 ` dpdklab
2025-08-19 7:03 ` dpdklab
2025-08-19 7:12 ` |PENDING| " dpdklab
2025-08-19 7:17 ` |WARNING| " dpdklab
2025-08-19 7:52 ` |FAILURE| " dpdklab
2025-08-19 7:54 ` dpdklab
2025-08-19 7:57 ` dpdklab
2025-08-19 7:57 ` |SUCCESS| " dpdklab
2025-08-19 8:05 ` dpdklab
2025-08-19 8:14 ` dpdklab
2025-08-19 8:30 ` |FAILURE| " dpdklab
2025-08-19 13:51 ` |WARNING| " dpdklab
2025-08-19 16:37 ` |FAILURE| " dpdklab
2025-08-19 16:43 ` dpdklab
2025-08-19 16:55 ` dpdklab
2025-08-19 16:59 ` dpdklab
2025-08-19 17:02 ` dpdklab
2025-08-19 17:20 ` 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=20250818233721.0B2EE125245@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).