From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Maher Sanalla <msanalla@nvidia.com>
Subject: Re: [PATCH rdma-next v1 0/3] Print link status when it is changed
Date: Thu, 06 Feb 2025 03:41:56 -0500 [thread overview]
Message-ID: <173883131613.836691.6835376998242287770.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1738586601.git.leon@kernel.org>
On Mon, 03 Feb 2025 14:48:03 +0200, Leon Romanovsky wrote:
> 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
> -----------------------------------------------------------------------
>
> [...]
Applied, thanks!
[1/3] IB/cache: Add log messages for IB device state changes
https://git.kernel.org/rdma/rdma/c/5459f6523c1f1a
[2/3] RDMA/core: Use ib_port_state_to_str() for IB state sysfs
https://git.kernel.org/rdma/rdma/c/1fd119c6db838d
[3/3] IB/hfi1: Remove state transition log message and opa_lstate_name()
https://git.kernel.org/rdma/rdma/c/d9d9434a3fee5c
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2025-02-06 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 12:48 [PATCH rdma-next v1 0/3] Print link status when it is changed Leon Romanovsky
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 ` Leon Romanovsky [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=173883131613.836691.6835376998242287770.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@ziepe.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox