From: David Ahern <dsahern@gmail.com>
To: Kory Maincent <kory.maincent@bootlin.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH iproute2-next 1/2] scripts: Add uapi header import script
Date: Tue, 16 Sep 2025 10:05:16 -0600 [thread overview]
Message-ID: <7d03fa72-b6ca-4f98-9f48-634ea45a0cc8@gmail.com> (raw)
In-Reply-To: <20250916180100.5f9db66d@kmaincent-XPS-13-7390>
On 9/16/25 10:01 AM, Kory Maincent wrote:
> On Tue, 16 Sep 2025 07:41:55 -0700
> Stephen Hemminger <stephen@networkplumber.org> wrote:
>
>> On Tue, 09 Sep 2025 15:21:42 +0200
>> Kory Maincent <kory.maincent@bootlin.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@bootlin.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,
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.
next prev parent reply other threads:[~2025-09-16 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:21 [PATCH iproute2-next 0/2] Add uapi header import script Kory Maincent
2025-09-09 13:21 ` [PATCH iproute2-next 1/2] scripts: " Kory Maincent
2025-09-11 20:57 ` David Ahern
2025-09-11 21:59 ` Stephen Hemminger
2025-09-16 14:40 ` Stephen Hemminger
2025-09-16 15:20 ` David Ahern
2025-09-16 14:41 ` Stephen Hemminger
2025-09-16 16:01 ` Kory Maincent
2025-09-16 16:05 ` David Ahern [this message]
2025-09-16 16:19 ` Kory Maincent
2025-09-09 13:21 ` [PATCH iproute2-next 2/2] Update kernel headers Kory Maincent
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=7d03fa72-b6ca-4f98-9f48-634ea45a0cc8@gmail.com \
--to=dsahern@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=thomas.petazzoni@bootlin.com \
/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).