From: Jason Gunthorpe <jgg@nvidia.com>
To: Gioh Kim <gi-oh.kim@ionos.com>
Cc: linux-rdma@vger.kernel.org, bvanassche@acm.org, leon@kernel.org,
dledford@redhat.com, haris.iqbal@ionos.com, jinpu.wang@ionos.com
Subject: Re: [PATCHv2 for-next 0/3] Improve debugging messages
Date: Tue, 13 Apr 2021 19:52:21 -0300 [thread overview]
Message-ID: <20210413225221.GB1376164@nvidia.com> (raw)
In-Reply-To: <20210406123639.202899-1-gi-oh.kim@ionos.com>
On Tue, Apr 06, 2021 at 02:36:36PM +0200, Gioh Kim wrote:
> Add more information into the error message for better debugging.
> The old messages was just like "Error happend" without detail
> information. This patch adds more information which session,
> port, HCA name and etc.
>
> V2->V1: add new line after variable block as requested by Jason
>
> Gioh Kim (3):
> RDMA/rtrs-clt: Print more info when an error happens
> RDMA/rtrs-srv: More debugging info when fail to send reply
> RDMA/rtrs-clt: Simplify error message
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2021-04-13 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 12:36 [PATCHv2 for-next 0/3] Improve debugging messages Gioh Kim
2021-04-06 12:36 ` [PATCHv2 for-next 1/3] RDMA/rtrs-clt: Print more info when an error happens Gioh Kim
2021-04-06 12:41 ` Leon Romanovsky
2021-04-09 9:57 ` Gioh Kim
2021-04-12 12:22 ` Jinpu Wang
2021-04-12 12:41 ` Leon Romanovsky
2021-04-12 12:53 ` Jinpu Wang
2021-04-12 14:00 ` Gioh Kim
2021-04-12 17:34 ` Leon Romanovsky
2021-04-13 5:31 ` Haakon Bugge
2021-04-13 6:43 ` Leon Romanovsky
2021-04-13 13:11 ` Gioh Kim
2021-04-13 19:31 ` Leon Romanovsky
2021-04-13 22:52 ` Jason Gunthorpe
2021-04-06 12:36 ` [PATCHv2 for-next 2/3] RDMA/rtrs-srv: More debugging info when fail to send reply Gioh Kim
2021-04-06 12:36 ` [PATCHv2 for-next 3/3] RDMA/rtrs-clt: Simplify error message Gioh Kim
2021-04-13 22:52 ` Jason Gunthorpe [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=20210413225221.GB1376164@nvidia.com \
--to=jgg@nvidia.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=gi-oh.kim@ionos.com \
--cc=haris.iqbal@ionos.com \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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.