From: patchwork-bot+netdevbpf@kernel.org
To: Nelson@ci.codeaurora.org, Shannon <shannon.nelson@amd.com>
Cc: dsahern@kernel.org, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, mst@redhat.com,
jasowang@redhat.com, si-wei.liu@oracle.com, allen.hubbe@amd.com,
drivers@pensando.io
Subject: Re: [PATCH iproute2] vdpa: consume device_features parameter
Date: Tue, 12 Sep 2023 16:00:30 +0000 [thread overview]
Message-ID: <169453443003.4554.2781113098793657141.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230911180815.820-1-shannon.nelson@amd.com>
Hello:
This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Mon, 11 Sep 2023 11:08:15 -0700 you 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"
>
> [...]
Here is the summary with links:
- [iproute2] vdpa: consume device_features parameter
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=92eac7e4bf14
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-09-12 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 18:08 [PATCH iproute2] vdpa: consume device_features parameter Shannon Nelson via Virtualization
2023-09-11 18:08 ` Shannon Nelson
2023-09-12 3:18 ` Jason Wang
2023-09-12 3:18 ` Jason Wang
2023-09-12 16:00 ` patchwork-bot+netdevbpf [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=169453443003.4554.2781113098793657141.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Nelson@ci.codeaurora.org \
--cc=allen.hubbe@amd.com \
--cc=drivers@pensando.io \
--cc=dsahern@kernel.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.com \
--cc=si-wei.liu@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.