DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: andremue@linux.microsoft.com,
	Thomas Monjalon <thomas@monjalon.net>,
	 Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] buildtools: prepare symbol check for Windows
Date: Fri, 26 Sep 2025 14:49:47 +0200	[thread overview]
Message-ID: <CAJFAV8xVEoKfsTJTwZeXbr63vn4BcRKg4XadEaWSaEJEMcmkuw@mail.gmail.com> (raw)
In-Reply-To: <20250925130438.3072610-1-david.marchand@redhat.com>

On Thu, 25 Sept 2025 at 15:05, David Marchand <david.marchand@redhat.com> wrote:
>
> The symbol check was implemented so far with shell scripts, relying
> on objdump and other unix tools preventing it from being run on Windows.
>
> There was also an ask from some maintainers to convert this type of
> developer checks to python scripts, to make it easier to extend and
> maintain.
>
> The new implementation still performs the four consistency checks:
> - symbols exported as experimental but missing __rte_experimental flag,
> - symbols flagged as experimental but missing export declaration,
> - symbols exported as internal but missing __rte_internal flag,
> - symbols flagged as internal but missing export declaration,
>
> The initial implementation was done relying on Claude Code
> (asking it to reimplement the existing check after it analysed
> the current build flow).
>
> I then cleaned up the python script, removed dumb comments, fixed coding
> style, fixed MAINTAINERS, fixed some dumb issues (like definition order in
> buildtools/meson.build).

Looks like trusting Claude on the python subtleties was not a good idea.
A v2 will be needed, but this change can wait to have a real user.
I'll mark as changes requested in patchwork.


-- 
David Marchand


      reply	other threads:[~2025-09-26 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 13:04 David Marchand
2025-09-26 12:49 ` David Marchand [this message]

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=CAJFAV8xVEoKfsTJTwZeXbr63vn4BcRKg4XadEaWSaEJEMcmkuw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=andremue@linux.microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).