From: patchwork-bot+netdevbpf@kernel.org
To: Donald Hunter <donald.hunter@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, jiri@resnulli.us,
jacob.e.keller@intel.com, liuhangbin@gmail.com,
donald.hunter@redhat.com
Subject: Re: [PATCH net-next v1] netlink/specs: Add VF attributes to rt_link spec
Date: Thu, 09 May 2024 01:50:27 +0000 [thread overview]
Message-ID: <171521942722.27440.17140123550559529904.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240507103603.23017-1-donald.hunter@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 May 2024 11:36:03 +0100 you wrote:
> Add support for retrieving VFs as part of link info. For example:
>
> ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/rt_link.yaml \
> --do getlink --json '{"ifi-index": 38, "ext-mask": ["vf", "skip-stats"]}'
> {'address': 'b6:75:91:f2:64:65',
> [snip]
> 'vfinfo-list': {'info': [{'broadcast': b'\xff\xff\xff\xff\xff\xff\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00',
> 'link-state': {'link-state': 'auto', 'vf': 0},
> 'mac': {'mac': b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00',
> 'vf': 0},
> 'rate': {'max-tx-rate': 0,
> 'min-tx-rate': 0,
> 'vf': 0},
> 'rss-query-en': {'setting': 0, 'vf': 0},
> 'spoofchk': {'setting': 0, 'vf': 0},
> 'trust': {'setting': 0, 'vf': 0},
> 'tx-rate': {'rate': 0, 'vf': 0},
> 'vlan': {'qos': 0, 'vf': 0, 'vlan': 0},
> 'vlan-list': {'info': [{'qos': 0,
> 'vf': 0,
> 'vlan': 0,
> 'vlan-proto': 0}]}},
> {'broadcast': b'\xff\xff\xff\xff\xff\xff\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00',
> 'link-state': {'link-state': 'auto', 'vf': 1},
> 'mac': {'mac': b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00'
> b'\x00\x00\x00\x00\x00\x00\x00\x00',
> 'vf': 1},
> 'rate': {'max-tx-rate': 0,
> 'min-tx-rate': 0,
> 'vf': 1},
> 'rss-query-en': {'setting': 0, 'vf': 1},
> 'spoofchk': {'setting': 0, 'vf': 1},
> 'trust': {'setting': 0, 'vf': 1},
> 'tx-rate': {'rate': 0, 'vf': 1},
> 'vlan': {'qos': 0, 'vf': 1, 'vlan': 0},
> 'vlan-list': {'info': [{'qos': 0,
> 'vf': 1,
> 'vlan': 0,
> 'vlan-proto': 0}]}}]},
> 'xdp': {'attached': 0}}
>
> [...]
Here is the summary with links:
- [net-next,v1] netlink/specs: Add VF attributes to rt_link spec
https://git.kernel.org/netdev/net-next/c/e497c3228a4e
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:[~2024-05-09 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 10:36 [PATCH net-next v1] netlink/specs: Add VF attributes to rt_link spec Donald Hunter
2024-05-09 1:50 ` 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=171521942722.27440.17140123550559529904.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=donald.hunter@redhat.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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 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.