From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw159681 [RFC v2] doc: add AGENTS.md for AI-powered code review tools
Date: Sat, 10 Jan 2026 19:02:31 +0100 (CET) [thread overview]
Message-ID: <20260110180231.3C68A123FA0@dpdk.org> (raw)
In-Reply-To: <20260110180038.11525-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159681
_coding style issues_
WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#138: FILE: AGENTS.md:1:
+# AGENTS.md - DPDK Code Review Guidelines for AI Tools
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#166: FILE: AGENTS.md:29:
+#include <stdio.h>
^^^^^
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#347: FILE: AGENTS.md:210:
+#include <stdio.h>
^^^^^
total: 0 errors, 3 warnings, 693 lines checked
__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_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.
__rte_internal must appear alone on the line immediately preceding the return type of a function.
Please use __rte_aligned only for struct or union types alignment.
Please use __rte_cache_aligned only for struct or union types alignment.
Please use __rte_cache_min_aligned only for struct or union types alignment.
Use __rte_packed_begin only after struct, union or alignment attributes.
__rte_packed_begin and __rte_packed_end should always be used in pairs.
next parent reply other threads:[~2026-01-10 18:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260110180038.11525-1-stephen@networkplumber.org>
2026-01-10 18:02 ` checkpatch [this message]
2026-01-10 19:05 ` |SUCCESS| " 0-day Robot
2026-01-10 19:05 ` 0-day Robot
2026-01-10 20:01 ` qemudev
2026-01-10 20:06 ` qemudev
2026-01-12 0:31 ` |SUCCESS| pw159681 [PATCH] [RFC,v2] doc: add AGENTS.md for AI-powere dpdklab
2026-01-12 0:35 ` |PENDING| " dpdklab
2026-01-12 0:39 ` |SUCCESS| " dpdklab
2026-01-12 0:40 ` dpdklab
2026-01-12 0:43 ` dpdklab
2026-01-12 0:48 ` |PENDING| " dpdklab
2026-01-12 1:06 ` |SUCCESS| " dpdklab
2026-01-12 1:13 ` |PENDING| " dpdklab
2026-01-12 1:21 ` |SUCCESS| " dpdklab
2026-01-12 1:25 ` dpdklab
2026-01-12 1:49 ` dpdklab
2026-01-12 2:07 ` dpdklab
2026-01-12 4:05 ` dpdklab
2026-01-12 4:05 ` dpdklab
2026-01-12 4:05 ` dpdklab
2026-01-12 4:05 ` dpdklab
2026-01-12 4:55 ` 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=20260110180231.3C68A123FA0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.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).