From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: dsahern@gmail.com, kuba@kernel.org, moshe@nvidia.com, saeedm@nvidia.com
Subject: [patch iproute2-next 0/2] devlink: get devlink port for ifname using RTNL get link command
Date: Mon, 7 Nov 2022 17:53:46 +0100 [thread overview]
Message-ID: <20221107165348.916092-1-jiri@resnulli.us> (raw)
From: Jiri Pirko <jiri@nvidia.com>
Patch #2 is benefiting of newly added IFLA_DEVLINK_PORT attribute
exposing netdev link to devlink port directly. Patch #1 is just
dependency for patch #2.
Jiri Pirko (2):
devlink: add ifname_map_add/del() helpers
devlink: get devlink port for ifname using RTNL get link command
devlink/devlink.c | 118 ++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 109 insertions(+), 9 deletions(-)
--
2.37.3
next reply other threads:[~2022-11-07 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 16:53 Jiri Pirko [this message]
2022-11-07 16:53 ` [patch iproute2-next 1/2] devlink: add ifname_map_add/del() helpers Jiri Pirko
2022-11-07 16:53 ` [patch iproute2-next 2/2] devlink: get devlink port for ifname using RTNL get link command Jiri Pirko
2022-11-09 12:10 ` Jiri Pirko
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=20221107165348.916092-1-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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