From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: oulijun <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Linuxarm <linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 【For help】 some tips for upstream the userspace driver code of hns_roce
Date: Fri, 14 Oct 2016 14:55:04 +0300 [thread overview]
Message-ID: <20161014115504.GG9282@leon.nu> (raw)
In-Reply-To: <58008835.3060403-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
On Fri, Oct 14, 2016 at 03:24:37PM +0800, oulijun wrote:
> Hi, Leon
> I have learned the guide and I am working it.
> I have learned the README.md in the branch of rdma-core.
> According to the instruction for building the user-space stack, it only
> support to build in Debian/Fedora/OpenSuSE/centos and ubuntu is not?
Did you install all required tools as mentioned in the readme?
I'm using Ubuntu and it builds on it perfectly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-14 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 8:09 【For help】 some tips for upstream the userspace driver code of hns_roce oulijun
[not found] ` <57FF414A.3000200-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-13 9:36 ` Leon Romanovsky
[not found] ` <20161013093659.GA9282-2ukJVAZIZ/Y@public.gmane.org>
2016-10-13 10:39 ` oulijun
2016-10-14 7:24 ` oulijun
[not found] ` <58008835.3060403-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-14 11:55 ` Leon Romanovsky [this message]
2016-10-17 11:29 ` oulijun
[not found] ` <5804B615.2010002-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-18 5:03 ` Leon Romanovsky
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=20161014115504.GG9282@leon.nu \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxarm-hv44wF8Li93QT0dZR+AlfA@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.