From: "Gaëtan Rivet" <grive@u256.net>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>, dev@dpdk.org
Cc: "Thomas Monjalon" <thomas@monjalon.net>,
"David Marchand" <david.marchand@redhat.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v1 2/3] devargs: make bus key parsing optional
Date: Tue, 19 Oct 2021 17:19:49 +0200 [thread overview]
Message-ID: <31a52f69-4a8a-4cc8-8445-45344ff4eb2c@www.fastmail.com> (raw)
In-Reply-To: <20211005155435.279043-3-xuemingl@nvidia.com>
On Tue, Oct 5, 2021, at 17:54, Xueming Li wrote:
> Global devargs syntax is used as device iteration filter like
> "class=vdpa", a devargs without bus args is valid from parsing
> perspective.
>
> This patch makes bus args optional.
>
> Fixes: d2a66ad79480 ("bus: add device arguments name parsing")
> Cc: stable@dpdk.org
I agree with the change, but I'm not sure it should go into stable.
The question goes further than that: is there a spec describing the valid
syntax to users, that would allow to say the current parsing is buggy?
I haven't found it in the doc.
If there is a change such as this one, it should also be notified in the release notes.
This is user-facing.
So, not saying you should do it and not part of this patch, but a doc might help
in doc/guides/howto maybe. The general grammar of a devargs could be formally
described (in BNF?).
Each layers should document their supported keys as well. Not sure it would be better
gathered in a single file or within each driver.
Now that the global syntax has been enabled for users, it should be documented.
>
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
For this patch and beside the stable considerations,
Reviewed-by: Gaetan Rivet <grive@u256.net>
--
Gaetan Rivet
prev parent reply other threads:[~2021-10-19 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211005123012.264727-1-xuemingl@nvidia.com>
2021-10-05 12:30 ` [dpdk-stable] [PATCH " Xueming Li
[not found] ` <20211005155435.279043-1-xuemingl@nvidia.com>
2021-10-05 15:54 ` [dpdk-stable] [PATCH v1 " Xueming Li
2021-10-19 15:19 ` Gaëtan Rivet [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=31a52f69-4a8a-4cc8-8445-45344ff4eb2c@www.fastmail.com \
--to=grive@u256.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.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).