From: Gal Pressman <galpress@amazon.com>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-next 0/4] EFA RDMA read support
Date: Sun, 20 Oct 2019 10:03:27 +0300 [thread overview]
Message-ID: <24527b2a-3bd2-cee5-0383-277c6e72af5c@amazon.com> (raw)
In-Reply-To: <20190910134301.4194-1-galpress@amazon.com>
On 10/09/2019 16:42, Gal Pressman wrote:
> Hi,
>
> The following series introduces RDMA read support and capabilities
> reporting to the EFA driver.
>
> The first two patches aren't directly related to RDMA read, but refactor
> some bits in the device capabilities struct.
>
> The last two patches add support for remote read access in MR
> registration and expose the RDMA read related attributes to the
> userspace library.
>
> PR was sent:
> https://github.com/linux-rdma/rdma-core/pull/576
Should I resubmit patches 2-4?
next prev parent reply other threads:[~2019-10-20 7:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 13:42 [PATCH for-next 0/4] EFA RDMA read support Gal Pressman
2019-09-10 13:42 ` [PATCH for-next 1/4] RDMA/efa: Fix incorrect error print Gal Pressman
2019-09-16 17:37 ` Jason Gunthorpe
2019-09-10 13:42 ` [PATCH for-next 2/4] RDMA/efa: Store network attributes in device attributes Gal Pressman
2019-09-10 13:43 ` [PATCH for-next 3/4] RDMA/efa: Support remote read access in MR registration Gal Pressman
2019-09-10 13:43 ` [PATCH for-next 4/4] RDMA/efa: Expose RDMA read related attributes Gal Pressman
2019-10-20 7:03 ` Gal Pressman [this message]
2019-10-21 17:31 ` [PATCH for-next 0/4] EFA RDMA read support Jason Gunthorpe
2019-10-23 9:55 ` Gal Pressman
2019-10-23 14:35 ` 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=24527b2a-3bd2-cee5-0383-277c6e72af5c@amazon.com \
--to=galpress@amazon.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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 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).