From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw156953 [PATCH] buildtools: prepare symbol check for Windows
Date: Thu, 25 Sep 2025 15:03:47 +0200 (CEST) [thread overview]
Message-ID: <20250925130347.8FB4612422E@dpdk.org> (raw)
In-Reply-To: <20250925130438.3072610-1-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/156953
_coding style issues_
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_internal must appear alone on the line immediately preceding the return type of a function.
__rte_internal must appear alone on the line immediately preceding the return type of a function.
next prev parent reply other threads:[~2025-09-25 13:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250925130438.3072610-1-david.marchand@redhat.com>
2025-09-25 12:31 ` |FAILURE| " qemudev
2025-09-25 13:03 ` checkpatch [this message]
2025-09-25 13:33 ` |PENDING| pw156953 [PATCH] buildtools: prepare symbol check for Wind dpdklab
2025-09-25 13:36 ` |SUCCESS| " dpdklab
2025-09-25 13:41 ` dpdklab
2025-09-25 13:42 ` |PENDING| " dpdklab
2025-09-25 13:44 ` dpdklab
2025-09-25 13:54 ` |SUCCESS| " dpdklab
2025-09-25 13:57 ` dpdklab
2025-09-25 13:57 ` dpdklab
2025-09-25 13:59 ` |PENDING| " dpdklab
2025-09-25 14:00 ` dpdklab
2025-09-25 14:11 ` |SUCCESS| " dpdklab
2025-09-25 14:19 ` |FAILURE| " dpdklab
2025-09-25 14:32 ` |WARNING| " dpdklab
2025-09-25 14:32 ` |FAILURE| " dpdklab
2025-09-25 14:37 ` |SUCCESS| " dpdklab
2025-09-25 14:48 ` dpdklab
2025-09-25 14:57 ` |SUCCESS| pw156953 [PATCH] buildtools: prepare symbol check for Windows 0-day Robot
2025-09-25 14:58 ` 0-day Robot
2025-09-25 14:59 ` |SUCCESS| pw156953 [PATCH] buildtools: prepare symbol check for Wind dpdklab
2025-09-25 18:43 ` dpdklab
2025-09-27 4:09 ` 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=20250925130347.8FB4612422E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=david.marchand@redhat.com \
--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).