From: Steve Wise <swise@opengridcomputing.com>
To: dsahern@gmail.com
Cc: leon@kernel.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH v3 iproute2-next 2/8] rdma: Makefile change to find <rdma/rdma_cma.h>
Date: Mon, 26 Mar 2018 13:57:33 -0700 [thread overview]
Message-ID: <a0f4455c51a4d19d3eab4b9ccd9426e7baf150d8.1522097991.git.swise@opengridcomputing.com> (raw)
In-Reply-To: <cover.1522097991.git.swise@opengridcomputing.com>
Signed-off-by: Steve Wise <swise@opengridcomputing.com>
---
rdma/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rdma/Makefile b/rdma/Makefile
index 819fcbe..2cb46b6 100644
--- a/rdma/Makefile
+++ b/rdma/Makefile
@@ -4,7 +4,7 @@ include ../config.mk
TARGETS :=
ifeq ($(HAVE_MNL),y)
-CFLAGS += -I./include/uapi/
+CFLAGS += -I./include/uapi/ -I./include/
RDMA_OBJ = rdma.o utils.o dev.o link.o res.o
--
1.8.3.1
next prev parent reply other threads:[~2018-03-26 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 20:59 [PATCH v3 iproute2-next 0/8] cm_id, cq, mr, and pd resource tracking Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 1/8] rdma: include rdma-core <rdma/rdma_cma.h> Steve Wise
2018-03-27 5:46 ` Leon Romanovsky
2018-03-27 13:23 ` David Ahern
2018-03-26 20:57 ` Steve Wise [this message]
2018-03-26 20:57 ` [PATCH v3 iproute2-next 3/8] rdma: update rdma_netlink.h Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 4/8] rdma: initialize the rd struct Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 5/8] rdma: Add CM_ID resource tracking information Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 6/8] rdma: Add CQ " Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 7/8] rdma: Add MR " Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 8/8] rdma: Add PD " Steve Wise
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=a0f4455c51a4d19d3eab4b9ccd9426e7baf150d8.1522097991.git.swise@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=dsahern@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).