From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 28/26] IB/ipath: Remove fast registration from the code
Date: Thu, 29 Oct 2015 11:49:50 -0400 [thread overview]
Message-ID: <5632401E.1090006@redhat.com> (raw)
In-Reply-To: <56323F02.8040803-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
On 10/29/2015 11:45 AM, Doug Ledford wrote:
> On 10/29/2015 11:33 AM, Sagi Grimberg wrote:
>> The driver does not support it anyway, and the support
>> should be added to a generic layer shared by both hfi1,
>> qib and softroce drivers.
>
> Thanks, applied.
Thanks for the quick turnaround Sagi, this has my compiles working again
with the final 26/26 patch back in place and lets me move on to other
patchsets.
I've pushed everything up to this point to k.o and github.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-10-29 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:33 [PATCH v5 27/26] IB/hfi1: Remove fast registration from the code Sagi Grimberg
[not found] ` <1446132812-20170-1-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-10-29 15:33 ` [PATCH 28/26] IB/ipath: " Sagi Grimberg
[not found] ` <1446132812-20170-2-git-send-email-sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-10-29 15:45 ` Doug Ledford
[not found] ` <56323F02.8040803-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-29 15:49 ` Doug Ledford [this message]
2015-10-29 15:44 ` [PATCH v5 27/26] IB/hfi1: " Doug Ledford
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=5632401E.1090006@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sagig-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 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).