All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Lijun Ou <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V3 rdma-core 0/5] Userspace library matching for hip08 RoCE
Date: Tue, 24 Oct 2017 18:28:36 +0300	[thread overview]
Message-ID: <20171024152836.GJ16127@mtr-leonro.local> (raw)
In-Reply-To: <1508851309-183263-1-git-send-email-oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 540 bytes --]

On Tue, Oct 24, 2017 at 09:21:44PM +0800, Lijun Ou wrote:
> This patch series add userspace library for hip08 RoCE driver. It will
> work with the kernel driver of hip08 RoCE(hns-roce-hw-v2.ko).
>
> Change from V2:
> - Fix the spelling with referred
> - Eliminate the warning by travis-CI
>
> Change from V1:
> - Fix build warning due to the strange placement of fprintf
>

I created pull request, but Travis CI doesn't seem like working.
https://github.com/linux-rdma/rdma-core/pull/230

I'll try to restart it a little bit later.

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-10-24 15:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 13:21 [PATCH V3 rdma-core 0/5] Userspace library matching for hip08 RoCE Lijun Ou
     [not found] ` <1508851309-183263-1-git-send-email-oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-10-24 13:21   ` [PATCH V3 rdma-core 1/5] libhns: Add new PCI device matching for hip08 Lijun Ou
2017-10-24 13:21   ` [PATCH V3 rdma-core 2/5] libhns: Introduce QP operations referred to hip08 RoCE device Lijun Ou
2017-10-24 13:21   ` [PATCH V3 rdma-core 3/5] libhns: Introduce CQ operations referred to hip08 device Lijun Ou
2017-10-24 13:21   ` [PATCH V3 rdma-core 4/5] libhns: Reimplement verbs of post_send and post_recv for hip08 RoCE Lijun Ou
2017-10-24 13:21   ` [PATCH V3 rdma-core 5/5] libhns: Update consolidate repo for userspace library of " Lijun Ou
2017-10-24 15:28   ` Leon Romanovsky [this message]
     [not found]     ` <20171024152836.GJ16127-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-25  5:38       ` [PATCH V3 rdma-core 0/5] Userspace library matching for " Leon Romanovsky
     [not found]         ` <20171025053833.GN16127-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-25  6:29           ` oulijun
     [not found]             ` <7689f70b-746a-44b8-91b3-81294d83b2a6-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-10-25  7:34               ` Leon Romanovsky
     [not found]                 ` <20171025073430.GO16127-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-25  9:28                   ` oulijun
     [not found]                     ` <40aa3621-b26b-8afc-7ce0-236659d9155c-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-10-25 16:18                       ` 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=20171024152836.GJ16127@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=oulijun-hv44wF8Li93QT0dZR+AlfA@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.