From: Jason Gunthorpe <jgg@ziepe•ca>
To: Danil Kipnis <danil.kipnis@cloud•ionos.com>
Cc: linux-rdma@vger•kernel.org, linux-next@vger•kernel.org,
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
Subject: Re: [PATCH 0/1] Fix RTRS compilation with block layer disabled
Date: Tue, 19 May 2020 20:34:22 -0300 [thread overview]
Message-ID: <20200519233422.GB12656@ziepe.ca> (raw)
In-Reply-To: <20200519080136.885628-1-danil.kipnis@cloud.ionos.com>
On Tue, May 19, 2020 at 10:01:35AM +0200, Danil Kipnis wrote:
> 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?
Yes, I will take them.
Do not send cover letters for single patches please
Jason
next prev parent reply other threads:[~2020-05-19 23:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 10:57 linux-next: Tree for May 18 Stephen Rothwell
2020-05-18 15:00 ` linux-next: Tree for May 18 (drivers/infiniband/ulp/rtrs/rtrs-clt.c) Randy Dunlap
2020-05-19 6:55 ` Danil Kipnis
2020-05-19 8:01 ` [PATCH 0/1] Fix RTRS compilation with block layer disabled Danil Kipnis
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 [this message]
2020-05-18 15:42 ` linux-next: Tree for May 18 (input/misc/iqs269a.c & regmap) Randy Dunlap
2020-05-18 16:20 ` Jeff LaBundy
2020-05-22 18:22 ` Randy Dunlap
2020-05-22 21:49 ` Dmitry Torokhov
2020-05-18 16:41 ` linux-next: Tree for May 18 (x86/mm/pgtable.c) Randy Dunlap
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=20200519233422.GB12656@ziepe.ca \
--to=jgg@ziepe$(echo .)ca \
--cc=axboe@kernel$(echo .)dk \
--cc=bvanassche@acm$(echo .)org \
--cc=danil.kipnis@cloud$(echo .)ionos.com \
--cc=dledford@redhat$(echo .)com \
--cc=jinpu.wang@cloud$(echo .)ionos.com \
--cc=leon@kernel$(echo .)org \
--cc=linux-block@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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