From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
dsahern@gmail.com, kuba@kernel.org, moshe@nvidia.com,
saeedm@nvidia.com
Subject: Re: [patch iproute2/net-next 0/4] devlink: optimize ifname handling
Date: Thu, 08 Dec 2022 17:50:15 +0000 [thread overview]
Message-ID: <167052181593.971.7294231283020849398.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221205122158.437522-1-jiri@resnulli.us>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Mon, 5 Dec 2022 13:21:54 +0100 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> This patchset enhances devlink tool to benefit from two recently
> introduces netlink changes in kernel:
>
> patch #2:
> Benefits from RT netlink extension by IFLA_DEVLINK_PORT attribute.
> Kernel sends devlink port handle info for every netdev.
> Use this attribute to directly obtain devlink port handle for ifname
> passed by user as a command line option.
>
> [...]
Here is the summary with links:
- [iproute2/net-next,1/4] devlink: add ifname_map_add/del() helpers
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=f04f5e1d08d9
- [iproute2/net-next,2/4] devlink: get devlink port for ifname using RTNL get link command
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=d5ae4c3fdba8
- [iproute2/net-next,3/4] devlink: push common code to __pr_out_port_handle_start_tb()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=18ff3ccbc853
- [iproute2/net-next,4/4] devlink: update ifname map when message contains DEVLINK_ATTR_PORT_NETDEV_NAME
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=42b27dfc6e72
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:[~2022-12-08 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 12:21 [patch iproute2/net-next 0/4] devlink: optimize ifname handling Jiri Pirko
2022-12-05 12:21 ` [patch iproute2/net-next 1/4] devlink: add ifname_map_add/del() helpers Jiri Pirko
2022-12-05 12:21 ` [patch iproute2/net-next 2/4] devlink: get devlink port for ifname using RTNL get link command Jiri Pirko
2022-12-08 19:00 ` Jacob Keller
2022-12-05 12:21 ` [patch iproute2/net-next 3/4] devlink: push common code to __pr_out_port_handle_start_tb() Jiri Pirko
2022-12-05 12:21 ` [patch iproute2/net-next 4/4] devlink: update ifname map when message contains DEVLINK_ATTR_PORT_NETDEV_NAME Jiri Pirko
2022-12-08 17: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=167052181593.971.7294231283020849398.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=stephen@networkplumber.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.