[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250916180100.5f9db66d@kmaincent-XPS-13-7390>
Date: Tue, 16 Sep 2025 18:01:00 +0200
From: Kory Maincent <kory.maincent@...tlin.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: David Ahern <dsahern@...il.com>, netdev@...r.kernel.org, Thomas
Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH iproute2-next 1/2] scripts: Add uapi header import
script
On Tue, 16 Sep 2025 07:41:55 -0700
Stephen Hemminger <stephen@...workplumber.org> wrote:
> On Tue, 09 Sep 2025 15:21:42 +0200
> Kory Maincent <kory.maincent@...tlin.com> wrote:
>
> > Add a script to automate importing Linux UAPI headers from kernel source.
> > The script handles dependency resolution and creates a commit with proper
> > attribution, similar to the ethtool project approach.
> >
> > Usage:
> > $ LINUX_GIT="$LINUX_PATH" iproute2-import-uapi [commit]
> >
> > Signed-off-by: Kory Maincent <kory.maincent@...tlin.com>
> > ---
>
> Script I use is much simpler.
The aim of my patch was to add a standard way of updating the uAPI header.
Indeed I supposed you maintainers, already have a script for that but for
developers that add support for new features they don't have such scripts.
People even may do it manually, even if I hope that's not the case.
We can see that the git commit messages on include/uapi/ are not
really consistent.
IMHO using the same script as ethtool was natural.
The final decision is your call but I think we should have a standard script
whatever it is.
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
Powered by blists - more mailing lists