All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] doc: add AGENTS.md for AI coding assistants
Date: Fri, 30 Jan 2026 15:46:35 -0800	[thread overview]
Message-ID: <20260130154635.7f2eb4f5@phoenix.local> (raw)
In-Reply-To: <20260124221439.234122-1-stephen@networkplumber.org>

On Sat, 24 Jan 2026 14:14:27 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:

> I (and probably others) are experimenting with AI code review
> and dumentation tools. It is worthwhile to have a baseline
> reference for coding assistants (such as Claude, Copilot,
> Cursor, etc.) when working with the iproute2 codebase.
> 
> This document is a first draft and covers:
> - Coding style based on Linux kernel guidelines with iproute2-specific
>   exceptions.
> - JSON output requirements using print_XXX helpers with PRINT_ANY
> - Command-line argument parsing (strcmp for new code, not matches())
> - Kernel compatibility and uapi header update procedures
> - Patch submission guidelines including DCO requirements
> 
> This helps ensure AI-generated contributions follow project conventions
> and reduces review burden from style issues. Changes and revisions
> are welcome and expected.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

Probably doing something in the review-prompts makes more sense
for iproute. I will look into that instead.

  parent reply	other threads:[~2026-01-30 23:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24 22:14 [PATCH iproute2-next] doc: add AGENTS.md for AI coding assistants Stephen Hemminger
2026-01-24 22:29 ` Andrew Lunn
2026-01-29  1:32   ` Stephen Hemminger
2026-01-30 23:46 ` Stephen Hemminger [this message]
2026-01-31 19:12 ` David Ahern
2026-01-31 19:40 ` Stephen Hemminger

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=20260130154635.7f2eb4f5@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.