From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Maher Sanalla <msanalla@nvidia.com>
Subject: [PATCH rdma-next v1 0/3] Print link status when it is changed
Date: Mon, 3 Feb 2025 14:48:03 +0200 [thread overview]
Message-ID: <cover.1738586601.git.leon@kernel.org> (raw)
Changelog:
v1:
* Changed print to include port number
* Don't print anything on change state from NOP
v0: https://lore.kernel.org/all/cover.1737290406.git.leon@kernel.org
-----------------------------------------------------------------------
In similar to netdev and hfi1 behavior, add general implementation to
IB/core to print IB port state changes.
"mlx5_core 0000:08:00.0 mlx5_0: Port: 1 Link DOWN"
"mlx5_core 0000:08:00.0 rdmap8s0f0: Port: 2 Link ACTIVE"
Thanks
Maher Sanalla (3):
IB/cache: Add log messages for IB device state changes
RDMA/core: Use ib_port_state_to_str() for IB state sysfs
IB/hfi1: Remove state transition log message and opa_lstate_name()
drivers/infiniband/core/cache.c | 6 ++++++
drivers/infiniband/core/sysfs.c | 14 +-------------
drivers/infiniband/hw/hfi1/chip.c | 18 ------------------
drivers/infiniband/hw/hfi1/chip.h | 1 -
drivers/infiniband/hw/hfi1/driver.c | 2 +-
drivers/infiniband/hw/hfi1/mad.c | 4 ++--
include/rdma/ib_verbs.h | 17 +++++++++++++++++
7 files changed, 27 insertions(+), 35 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-03 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 12:48 Leon Romanovsky [this message]
2025-02-03 12:48 ` [PATCH rdma-next v1 1/3] IB/cache: Add log messages for IB device state changes Leon Romanovsky
2025-02-03 12:48 ` [PATCH rdma-next v1 2/3] RDMA/core: Use ib_port_state_to_str() for IB state sysfs Leon Romanovsky
2025-02-03 12:48 ` [PATCH rdma-next v1 3/3] IB/hfi1: Remove state transition log message and opa_lstate_name() Leon Romanovsky
2025-02-06 8:41 ` [PATCH rdma-next v1 0/3] Print link status when it is changed Leon Romanovsky
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=cover.1738586601.git.leon@kernel.org \
--to=leon@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=msanalla@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 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.