From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Igor Russkikh <irusskikh@marvell.com>,
Potnuri Bharat Teja <bharat@chelsio.com>
Subject: Re: [PATCH v2 07/12] devtools: check VMDq capability
Date: Thu, 22 Oct 2026 11:44:37 +0200 [thread overview]
Message-ID: <Nskh3lQbTOWC4SgPkE2x7w@monjalon.net> (raw)
In-Reply-To: <20261021103027.2050351-8-david.marchand@redhat.com>
21/10/2026 12:30, David Marchand:
> --- a/devtools/check-doc-vs-code.sh
> +++ b/devtools/check-doc-vs-code.sh
> @@ -78,6 +78,28 @@ driver_code_dir() # <driver>
> esac
> }
>
> +doc_code_map=","
What is this comma?
> +for d in $rootdir/doc/guides/nics/features/*.ini; do
> + drv=$(basename "$d" .ini)
> + code=$(driver_code_dir $drv)
> + case $doc_code_map in
> + *,$code:*)
> + before=${doc_code_map%,$code:*}
> + after=${doc_code_map#*,$code:}
> + drivers=${after%%,*}
> + rest=${after#*,}
> + doc_code_map="$before,$code:$drivers $drv,$rest" ;;
> + *)
> + doc_code_map="$doc_code_map$code: $drv," ;;
> + esac
> +done
Please add a comment for this block to explain the goal.
> +
> +docs_for_code() # <code_dir>
Even the name of this function is not self-explanatory.
> +{
> + tmp=${doc_code_map#*,$1:}
> + echo ${tmp%%,*}
> +}
[...]
> +all_docs_agree() # <driver> <feature>
all docs agree on what?
a doc is supposed to refer to a single code path
> +{
> + code=$(driver_code_dir $1)
> + first=""
> + for drv in $(docs_for_code $code); do
> + d=$rootdir/doc/guides/nics/features/$drv.ini
> + has_doc_feature "$d" "$2" && val=true || val=false
> + [ -n "$first" ] || first=$val
> + [ "$first" = "$val" ] || return 1
> + done
> + return 0
> +}
> +
next prev parent reply other threads:[~2026-10-22 9:44 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 13:05 [PATCH 0/8] Validate multiqueue configuration in ethdev David Marchand
2026-10-16 13:05 ` [PATCH 1/8] net/bnxt: remove leftover VMDq code in MAC helpers David Marchand
2026-10-16 13:05 ` [PATCH 2/8] drivers/net: fix reported VMDq capability David Marchand
2026-10-16 13:05 ` [PATCH 3/8] drivers/net: remove check on VMDq modes David Marchand
2026-10-16 13:05 ` [PATCH 4/8] devtools: check VMDq capability David Marchand
2026-10-16 13:05 ` [PATCH 5/8] ethdev: check DCB availability David Marchand
2026-10-16 13:05 ` [PATCH 6/8] drivers/net: fix reported RSS capability David Marchand
2026-10-16 13:05 ` [PATCH 7/8] ethdev: check RSS availability David Marchand
2026-10-16 13:05 ` [PATCH 8/8] ethdev: check unknown Rx/Tx multi-queue modes David Marchand
2026-10-16 16:44 ` [PATCH 0/8] Validate multiqueue configuration in ethdev Stephen Hemminger
2026-10-19 6:41 ` Renyong Wan
2026-10-21 10:30 ` [PATCH v2 00/12] " David Marchand
2026-10-21 10:30 ` [PATCH v2 01/12] devtools: fix matching in doc check David Marchand
2026-10-21 10:42 ` Thomas Monjalon
2026-10-21 10:30 ` [PATCH v2 02/12] doc: fix L2TPv2 and PPP matching support for ICE David Marchand
2026-10-21 10:30 ` [PATCH v2 03/12] devtools: handle multiple drivers in doc check David Marchand
2026-10-22 9:39 ` Thomas Monjalon
2026-10-21 10:30 ` [PATCH v2 04/12] net/bnxt: remove leftover VMDq code in MAC helpers David Marchand
2026-10-21 10:30 ` [PATCH v2 05/12] drivers/net: fix reported VMDq capability David Marchand
2026-10-21 10:53 ` Bruce Richardson
2026-10-21 10:30 ` [PATCH v2 06/12] drivers/net: remove check on VMDq modes David Marchand
2026-10-21 10:55 ` Bruce Richardson
2026-10-21 10:30 ` [PATCH v2 07/12] devtools: check VMDq capability David Marchand
2026-10-22 9:44 ` Thomas Monjalon [this message]
2026-10-21 10:30 ` [PATCH v2 08/12] doc: fix DCB capability for some Intel drivers David Marchand
2026-10-21 11:04 ` Bruce Richardson
2026-10-21 10:30 ` [PATCH v2 09/12] ethdev: check DCB availability David Marchand
2026-10-21 11:07 ` Bruce Richardson
2026-10-21 10:30 ` [PATCH v2 10/12] drivers/net: fix reported RSS capability David Marchand
2026-10-22 6:17 ` Renyong Wan
2026-10-21 10:30 ` [PATCH v2 11/12] ethdev: check RSS availability David Marchand
2026-10-21 10:30 ` [PATCH v2 12/12] ethdev: check unknown Rx/Tx multi-queue modes David Marchand
2026-10-21 17:42 ` [PATCH v2 00/12] Validate multiqueue configuration in ethdev Stephen Hemminger
2026-10-22 17:44 ` [PATCH v3 00/13] " David Marchand
2026-10-22 17:44 ` [PATCH v3 01/13] devtools: fix matching in doc check David Marchand
2026-10-22 17:44 ` [PATCH v3 02/13] doc: fix L2TPv2 and PPP matching support for ICE David Marchand
2026-10-22 17:44 ` [PATCH v3 03/13] devtools: support Intel drivers in doc check David Marchand
2026-10-23 10:11 ` Thomas Monjalon
2026-10-22 17:44 ` [PATCH v3 04/13] devtools: handle multiple " David Marchand
2026-10-23 10:13 ` Thomas Monjalon
2026-10-23 15:08 ` David Marchand
2026-10-22 17:44 ` [PATCH v3 05/13] net/bnxt: remove leftover VMDq code in MAC helpers David Marchand
2026-10-22 17:44 ` [PATCH v3 06/13] drivers/net: fix reported VMDq capability David Marchand
2026-10-22 17:44 ` [PATCH v3 07/13] drivers/net: remove check on VMDq modes David Marchand
2026-10-27 2:38 ` fengchengwen
2026-10-22 17:44 ` [PATCH v3 08/13] devtools: check VMDq capability David Marchand
2026-10-22 17:44 ` [PATCH v3 09/13] doc: fix DCB capability for some Intel drivers David Marchand
2026-10-22 17:44 ` [PATCH v3 10/13] ethdev: check DCB availability David Marchand
2026-10-27 2:39 ` fengchengwen
2026-10-22 17:44 ` [PATCH v3 11/13] drivers/net: fix reported RSS capability David Marchand
2026-10-22 17:44 ` [PATCH v3 12/13] ethdev: check RSS availability David Marchand
2026-10-27 2:41 ` fengchengwen
2026-10-22 17:44 ` [PATCH v3 13/13] ethdev: check unknown Rx/Tx multi-queue modes David Marchand
2026-10-26 18:11 ` [PATCH v3 00/13] Validate multiqueue configuration in ethdev Stephen Hemminger
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=Nskh3lQbTOWC4SgPkE2x7w@monjalon.net \
--to=thomas@monjalon.net \
--cc=bharat@chelsio.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=irusskikh@marvell.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