[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250916181953.1c0aa4ee@kmaincent-XPS-13-7390>
Date: Tue, 16 Sep 2025 18:19:53 +0200
From: Kory Maincent <kory.maincent@...tlin.com>
To: David Ahern <dsahern@...il.com>
Cc: Stephen Hemminger <stephen@...workplumber.org>, 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 10:05:16 -0600
David Ahern <dsahern@...il.com> wrote:
> On 9/16/25 10:01 AM, Kory Maincent wrote:
> > 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:
> >>
> [...]
> >>
> >> 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,
>
> There are separate needs.
>
> I sync include/uapi for iproute2-next based on net-next. rdma and vdpa
> have separate -next trees which is why they have their own include/uapi
> directories. This script makes this part much easier for me hence why I
> merged it.
>
> Stephen will ensure all uapi headers match the kernel release meaning
> Linus' tree.
Oh, ok. Thanks for the clarification.
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
Powered by blists - more mailing lists