From: David Ahern <dsahern@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Michael Guralnik <michaelgur@mellanox.com>,
netdev <netdev@vger.kernel.org>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: [PATCH iproute2-next] rdma: Add print of link CapabilityMask2 flags
Date: Thu, 27 Dec 2018 18:42:56 -0500 [thread overview]
Message-ID: <b24da4da-1bfa-a9ca-ae18-c9f4cb932c13@gmail.com> (raw)
In-Reply-To: <20181223112419.29157-1-leon@kernel.org>
On 12/23/18 6:24 AM, Leon Romanovsky wrote:
> From: Michael Guralnik <michaelgur@mellanox.com>
>
> CapabilityMask2 is defined in IBTA spec as a member of PortInfo.
> Add translation to string of new CapabilityMask2 expansion of link caps.
>
> The flags are concatenated to current caps print as seen in this example
> printing EXT_INFO flag:
>
> root@server-22 $ rdma -d link
> 1/1: mlx5_0/1: subnet_prefix fe80:0000:0000:0000 lid 2 sm_lid 2 lmc 0
> state ACTIVE physical_state LINK_UP
> caps: <SM, TRAP, SL_MAP, SYS_IMAGE_GUID, CABLE_INFO, EXTENDED_SPEEDS,
> CAP_MASK2, CM, DEVICE_MGMT, VENDOR_CLASS, CAP_MASK_NOTICE,
> CLIENT_REG, OTHER_LOCAL_CHANGES, MULT_PKER_TRAP, EXT_INFO>
>
> Signed-off-by: Michael Guralnik <michaelgur@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
> rdma/link.c | 36 +++++++++++++++++++++++++++++++-----
> 1 file changed, 31 insertions(+), 5 deletions(-)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2018-12-27 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 11:24 [PATCH iproute2-next] rdma: Add print of link CapabilityMask2 flags Leon Romanovsky
2018-12-27 23:42 ` David Ahern [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=b24da4da-1bfa-a9ca-ae18-c9f4cb932c13@gmail.com \
--to=dsahern@gmail.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=michaelgur@mellanox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).