From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH 0/6] devtools: improve Linux uAPI script
Date: Mon, 08 Sep 2025 11:42:27 +0200 [thread overview]
Message-ID: <13838928.uLZWGnKmhe@thomas> (raw)
In-Reply-To: <20250827082413.1417226-1-thomas@monjalon.net>
27/08/2025 10:21, Thomas Monjalon:
> The main goal of this series is to check Linux uAPI headers quietly.
> While doing so, few minor improvements are done.
>
> Thomas Monjalon (6):
> devtools: remove superfluous curly braces in uAPI script
> devtools: remove superfluous fallbacks in uAPI script
> devtools: move uAPI processing into functions
> devtools: remove unused variables in uAPI script
> devtools: make uAPI check exclusive to other options
> devtools: add quiet mode in uAPI script
>
> devtools/linux-uapi.sh | 146 ++++++++++++++++++++++-------------------
> 1 file changed, 80 insertions(+), 66 deletions(-)
Applied
prev parent reply other threads:[~2025-09-08 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 8:21 Thomas Monjalon
2025-08-27 8:21 ` [PATCH 1/6] devtools: remove superfluous curly braces in " Thomas Monjalon
2025-09-03 13:39 ` Maxime Coquelin
2025-08-27 8:21 ` [PATCH 2/6] devtools: remove superfluous fallbacks " Thomas Monjalon
2025-09-03 13:47 ` Maxime Coquelin
2025-08-27 8:21 ` [PATCH 3/6] devtools: move uAPI processing into functions Thomas Monjalon
2025-09-03 13:50 ` Maxime Coquelin
2025-08-27 8:21 ` [PATCH 4/6] devtools: remove unused variables in uAPI script Thomas Monjalon
2025-09-03 13:50 ` Maxime Coquelin
2025-08-27 8:21 ` [PATCH 5/6] devtools: make uAPI check exclusive to other options Thomas Monjalon
2025-09-03 13:52 ` Maxime Coquelin
2025-08-27 8:21 ` [PATCH 6/6] devtools: add quiet mode in uAPI script Thomas Monjalon
2025-09-03 13:54 ` Maxime Coquelin
2025-09-08 9:41 ` Thomas Monjalon
2025-09-08 9:42 ` Thomas Monjalon [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=13838928.uLZWGnKmhe@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).