From: Danil Kipnis <danil.kipnis@cloud.ionos.com>
To: linux-rdma@vger.kernel.org, jgg@ziepe.ca, linux-next@vger.kernel.org
Cc: jinpu.wang@cloud.ionos.com, dledford@redhat.com, axboe@kernel.dk,
linux-block@vger.kernel.org, bvanassche@acm.org,
rdunlap@infradead.org, leon@kernel.org,
Danil Kipnis <danil.kipnis@cloud.ionos.com>
Subject: [PATCH 0/1] Fix RTRS compilation with block layer disabled
Date: Tue, 19 May 2020 10:01:35 +0200 [thread overview]
Message-ID: <20200519080136.885628-1-danil.kipnis@cloud.ionos.com> (raw)
In-Reply-To: <e132ee19-ff55-c017-732c-284a3b20daf7@infradead.org>
Hi Jason, Hi All,
this fixes the compilation problem reported by Randy Dunlap for RTRS on
rdma for-next.
Jason, am I even doing the right thing sending the fixes for the issues
reported for the for-next for RTRS/RNBD to here?
Danil Kipnis (1):
rnbd/rtrs: pass max segment size from blk user to the rdma library
drivers/block/rnbd/rnbd-clt.c | 1 +
drivers/infiniband/ulp/rtrs/rtrs-clt.c | 17 +++++++++++------
drivers/infiniband/ulp/rtrs/rtrs-clt.h | 1 +
drivers/infiniband/ulp/rtrs/rtrs.h | 1 +
4 files changed, 14 insertions(+), 6 deletions(-)
--
2.25.1
next parent reply other threads:[~2020-05-19 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e132ee19-ff55-c017-732c-284a3b20daf7@infradead.org>
2020-05-19 8:01 ` Danil Kipnis [this message]
2020-05-19 8:01 ` [PATCH 1/1] rnbd/rtrs: pass max segment size from blk user to the rdma library Danil Kipnis
2020-05-19 8:48 ` Leon Romanovsky
2020-05-19 9:14 ` Danil Kipnis
2020-05-19 15:42 ` Leon Romanovsky
2020-05-19 11:14 ` [PATCH v2] " Danil Kipnis
2020-05-19 15:04 ` Randy Dunlap
2020-05-19 23:44 ` Jason Gunthorpe
2020-05-21 16:12 ` Randy Dunlap
2020-05-21 20:00 ` Jason Gunthorpe
2020-05-19 8:45 ` [PATCH 0/1] Fix RTRS compilation with block layer disabled Leon Romanovsky
2020-05-19 23:34 ` 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=20200519080136.885628-1-danil.kipnis@cloud.ionos.com \
--to=danil.kipnis@cloud.ionos.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@cloud.ionos.com \
--cc=leon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rdunlap@infradead.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).