From: Md Haris Iqbal <haris.iqbal@ionos.com>
To: linux-rdma@vger.kernel.org
Cc: bvanassche@acm.org, leon@kernel.org, dledford@redhat.com,
jgg@ziepe.ca, haris.iqbal@ionos.com, jinpu.wang@ionos.com
Subject: [PATCH for-next 0/5] Misc update for RTRS
Date: Fri, 14 Jan 2022 16:47:48 +0100 [thread overview]
Message-ID: <20220114154753.983568-1-haris.iqbal@ionos.com> (raw)
Hi Jason, hi Doug,
Please consider to include following changes to the next merge window.
The patchset is organized as:
- patch1, patch2, patch3 fixes warnings generated from checkpatch
- patch4 updates a comment.
- patch5 In case of error, performs failover earlier & avoids deadlock
Gioh Kim (3):
RDMA/rtrs: fix CHECK:BRACES type warning
RDMA/rtrs-clt: fix CHECK type warnings
RDMA/rtrs-clt: fix CHECK type warnings
Jack Wang (2):
RDMA/rtrs-clt: Update one outdated comment in path_it_deinit
RDMA/rtrs-clt: Do stop and failover outside reconnect work.
drivers/infiniband/ulp/rtrs/rtrs-clt-sysfs.c | 3 +-
drivers/infiniband/ulp/rtrs/rtrs-clt.c | 91 ++++++++++----------
drivers/infiniband/ulp/rtrs/rtrs-clt.h | 1 +
drivers/infiniband/ulp/rtrs/rtrs.c | 1 -
4 files changed, 47 insertions(+), 49 deletions(-)
--
2.25.1
next reply other threads:[~2022-01-14 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 15:47 Md Haris Iqbal [this message]
2022-01-14 15:47 ` [PATCH for-next 1/5] RDMA/rtrs: fix CHECK:BRACES type warning Md Haris Iqbal
2022-01-14 15:47 ` [PATCH for-next 2/5] RDMA/rtrs-clt: fix CHECK type warnings Md Haris Iqbal
2022-01-28 14:55 ` Jason Gunthorpe
2022-02-07 16:07 ` Haris Iqbal
2022-01-14 15:47 ` [PATCH for-next 3/5] " Md Haris Iqbal
2022-01-14 15:47 ` [PATCH for-next 4/5] RDMA/rtrs-clt: Update one outdated comment in path_it_deinit Md Haris Iqbal
2022-01-14 15:47 ` [PATCH for-next 5/5] RDMA/rtrs-clt: Do stop and failover outside reconnect work Md Haris Iqbal
2022-01-26 13:56 ` [PATCH for-next 0/5] Misc update for RTRS Haris Iqbal
2022-01-28 15:00 ` Jason Gunthorpe
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=20220114154753.983568-1-haris.iqbal@ionos.com \
--to=haris.iqbal@ionos.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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.