From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Daniel Jurgens <danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Parav Pandit <parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-next 0/4] DMAC RoCE refacting code
Date: Mon, 15 Jan 2018 16:07:10 -0700 [thread overview]
Message-ID: <20180115230710.GD1867@ziepe.ca> (raw)
In-Reply-To: <20180109132453.29038-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Tue, Jan 09, 2018 at 03:24:49PM +0200, Leon Romanovsky wrote:
> Hi,
>
> The following series is refactoring code for DMAC RoCE code and one fix
> to perform modify QP on real QP.
>
> Thanks
>
> Parav Pandit (4):
> IB/core: Perform modify QP on real one
> IB/core: Limit DMAC resolution to userspace QPs
> IB/core: Attempt DMAC resolution for only RoCE
> IB/core: Limit DMAC resolution to RoCE Connected QPs
I applied all of these to for-next
Thanks,
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-01-15 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 13:24 [PATCH rdma-next 0/4] DMAC RoCE refacting code Leon Romanovsky
[not found] ` <20180109132453.29038-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-09 13:24 ` [PATCH rdma-next 1/4] IB/core: Perform modify QP on real one Leon Romanovsky
2018-01-09 13:24 ` [PATCH rdma-next 2/4] IB/core: Limit DMAC resolution to userspace QPs Leon Romanovsky
2018-01-09 13:24 ` [PATCH rdma-next 3/4] IB/core: Attempt DMAC resolution for only RoCE Leon Romanovsky
2018-01-09 13:24 ` [PATCH rdma-next 4/4] IB/core: Limit DMAC resolution to RoCE Connected QPs Leon Romanovsky
2018-01-15 23:07 ` 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=20180115230710.GD1867@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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.