From: Parav Pandit <parav@nvidia.com>
To: <netdev@vger.kernel.org>, <stephen@networkplumber.org>,
<dsahern@kernel.org>
Cc: Parav Pandit <parav@nvidia.com>
Subject: [PATCH net-next 0/3] devlink show controller and external info
Date: Fri, 18 Sep 2020 11:02:57 +0300 [thread overview]
Message-ID: <20200918080300.35132-1-parav@nvidia.com> (raw)
For certain devlink port flavours controller number and optionally external attributes are reported by the kernel.
(a) controller number indicates that a given port belong to which local or external controller.
(b) external port attribute indicates that if a given port is for external or local controller.
This short series shows this attributes to user.
Patch summary:
Patch-1 updates the kernel header
Patch-2 shows external attribute
Patch-3 show controller number
Parav Pandit (3):
devlink: Update kernel headers
devlink: Show external port attribute
devlink: Show controller number of a devlink port
devlink/devlink.c | 9 +++++++++
include/uapi/linux/devlink.h | 4 ++++
2 files changed, 13 insertions(+)
--
2.26.2
next reply other threads:[~2020-09-18 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 8:02 Parav Pandit [this message]
2020-09-18 8:02 ` [PATCH net-next 1/3] devlink: Update kernel headers Parav Pandit
2020-09-18 8:02 ` [PATCH net-next 2/3] devlink: Show external port attribute Parav Pandit
2020-09-18 8:03 ` [PATCH net-next 3/3] devlink: Show controller number of a devlink port Parav Pandit
2020-09-18 10:08 ` [PATCH net-next 0/3] devlink show controller and external info Parav Pandit
2020-09-18 10:16 ` [PATCH iproute2-next RESEND " Parav Pandit
2020-09-18 10:16 ` [PATCH iproute2-next RESEND 1/3] devlink: Update kernel headers Parav Pandit
2020-09-18 10:16 ` [PATCH iproute2-next RESEND 2/3] devlink: Show external port attribute Parav Pandit
2020-09-18 10:16 ` [PATCH iproute2-next RESEND 3/3] devlink: Show controller number of a devlink port Parav Pandit
2020-09-23 2:21 ` [PATCH iproute2-next RESEND 0/3] devlink show controller and external info David Ahern
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=20200918080300.35132-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--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.