From: Jason Wang <jasowang@redhat.com>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: dsahern@kernel.org, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, mst@redhat.com,
allen.hubbe@amd.com, drivers@pensando.io
Subject: Re: [PATCH] vdpa: consume device_features parameter
Date: Wed, 17 May 2023 13:56:33 +0800 [thread overview]
Message-ID: <CACGkMEu2d2ap_jzUGH8MpLZvscEPGZLtDxRqM2gjPQ43GS1B1g@mail.gmail.com> (raw)
In-Reply-To: <29db10bca7e5ef6b1137282292660fc337a4323a.1683907102.git.allen.hubbe@amd.com>
On Sat, May 13, 2023 at 12:42 AM Shannon Nelson <shannon.nelson@amd.com> wrote:
>
> From: Allen Hubbe <allen.hubbe@amd.com>
>
> Consume the parameter to device_features when parsing command line
> options. Otherwise the parameter may be used again as an option name.
>
> # vdpa dev add ... device_features 0xdeadbeef mac 00:11:22:33:44:55
> Unknown option "0xdeadbeef"
>
> Fixes: a4442ce58ebb ("vdpa: allow provisioning device features")
> Signed-off-by: Allen Hubbe <allen.hubbe@amd.com>
> Reviewed-by: Shannon Nelson <shannon.nelson@amd.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Thanks
> ---
> vdpa/vdpa.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/vdpa/vdpa.c b/vdpa/vdpa.c
> index 27647d73d498..8a2fca8647b6 100644
> --- a/vdpa/vdpa.c
> +++ b/vdpa/vdpa.c
> @@ -353,6 +353,8 @@ static int vdpa_argv_parse(struct vdpa *vdpa, int argc, char **argv,
> &opts->device_features);
> if (err)
> return err;
> +
> + NEXT_ARG_FWD();
> o_found |= VDPA_OPT_VDEV_FEATURES;
> } else {
> fprintf(stderr, "Unknown option \"%s\"\n", *argv);
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-05-17 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 16:41 [PATCH] vdpa: consume device_features parameter Shannon Nelson
2023-05-17 5:56 ` Jason Wang [this message]
2023-05-18 6:51 ` Eugenio Perez Martin
2023-09-07 20:41 ` Si-Wei Liu
2023-09-07 23:02 ` Nelson, Shannon
2023-09-08 0:07 ` David Ahern
2023-09-08 18:37 ` Si-Wei Liu
2023-09-09 20:36 ` David Ahern
2023-09-12 0:33 ` Si-Wei Liu
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=CACGkMEu2d2ap_jzUGH8MpLZvscEPGZLtDxRqM2gjPQ43GS1B1g@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=allen.hubbe@amd.com \
--cc=drivers@pensando.io \
--cc=dsahern@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.com \
--cc=virtualization@lists.linux-foundation.org \
/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).