From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 0/2] Improve AI review feedback
Date: Fri, 4 Sep 2026 09:23:06 -0700 [thread overview]
Message-ID: <20260904162454.218213-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20260829171822.305500-1-stephen@networkplumber.org>
Existing AI review used by CI generates lots of false
positives from lack of confidence and poor parsing.
This still doesn't make up for the missing tooling, where running
AI review locally or in GUI gives better results. But these
changes should reduce the bogus warnings.
Stephen Hemminger (2):
AGENTS: reduce false positives
devtools/ai/review-patch: reduce spurious warnings
AGENTS.md | 278 +++++++++++++++++++++++++++++++-----
devtools/ai/review-patch.py | 232 ++++++++++++++++++++++++------
2 files changed, 425 insertions(+), 85 deletions(-)
--
2.53.0
next prev parent reply other threads:[~2026-09-04 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 17:18 [PATCH] AGENTS: reduce false positives Stephen Hemminger
2026-09-04 16:23 ` Stephen Hemminger [this message]
2026-09-04 16:23 ` [PATCH v2 1/2] " Stephen Hemminger
2026-09-04 16:23 ` [PATCH v2 2/2] devtools/ai/review-patch: reduce spurious warnings Stephen Hemminger
2026-09-08 12:31 ` Aaron Conole
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=20260904162454.218213-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@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