From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Yigal Korman <yigal@plexistor.com>,
mmarek@suse.com, linux-kbuild@vger.kernel.org,
dhowells@redhat.com,
Linux RDMA Mailing List <linux-rdma@vger.kernel.org>
Subject: Re: Possible rdma-core header conflict
Date: Thu, 24 Aug 2017 18:34:56 +0300 [thread overview]
Message-ID: <20170824153456.GM1724@mtr-leonro.local> (raw)
In-Reply-To: <20170824152713.GB23110@obsidianresearch.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Thu, Aug 24, 2017 at 09:27:13AM -0600, Jason Gunthorpe wrote:
> On Thu, Aug 24, 2017 at 03:23:28PM +0300, Leon Romanovsky wrote:
>
> > For the development, I use ability of rdma-core to run everything in
> > place and I don't install anything. I compile with build.sh supplied
> > in rdma-core and adjust Makefiles to point to build/lib|include directories
> > without need to install.
>
> For development you can also tell rdma-core to refer to the kernel
> source tree directly and it will immediately use those kernel
> header for RDMA. No need to install things and wreck your distro.
>
> # -DKERNEL_DIR='.../linux' (default '')
> # If set use the kernel UAPI headers from this kernel source
> # tree.
>
We need to change default to '.../linux-rdma', so it will work
out of the box for me :)
> Jason
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-08-24 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACTTzNa3EzABie9=h2X-ONBefyaoWE1+RAT-T+uxJVvVij15Rg@mail.gmail.com>
[not found] ` <20170821120310.GL1724@mtr-leonro.local>
[not found] ` <20170821155729.GC4401@obsidianresearch.com>
2017-08-22 6:08 ` Possible rdma-core header conflict Yigal Korman
2017-08-22 6:47 ` Leon Romanovsky
2017-08-24 10:50 ` Leon Romanovsky
2017-08-24 11:28 ` Yigal Korman
2017-08-24 12:23 ` Leon Romanovsky
2017-08-24 15:27 ` Jason Gunthorpe
2017-08-24 15:34 ` Leon Romanovsky [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=20170824153456.GM1724@mtr-leonro.local \
--to=leon@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=yigal@plexistor.com \
/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