From: Greg Thelen <gthelen@google.com>
To: dennis.dalessandro@intel.com,
Bart Van Assche <Bart.VanAssche@wdc.com>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Thelen <gthelen@google.com>,
Tarick Bedeir <tarick@google.com>
Subject: [PATCH v3] IB: make INFINIBAND_ADDR_TRANS configurable
Date: Sat, 14 Apr 2018 08:36:42 -0700 [thread overview]
Message-ID: <20180414153642.28178-1-gthelen@google.com> (raw)
In-Reply-To: <CAHH2K0YTCa99ZfCdvq0WEJVvszo7+kUiVP_cz0igqE4TZSNYGQ@mail.gmail.com>
Allow INFINIBAND without INFINIBAND_ADDR_TRANS.
Signed-off-by: Greg Thelen <gthelen@google.com>
Cc: Tarick Bedeir <tarick@google.com>
---
drivers/infiniband/Kconfig | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/Kconfig b/drivers/infiniband/Kconfig
index ee270e065ba9..2a972ed6851b 100644
--- a/drivers/infiniband/Kconfig
+++ b/drivers/infiniband/Kconfig
@@ -61,9 +61,12 @@ config INFINIBAND_ON_DEMAND_PAGING
pages on demand instead.
config INFINIBAND_ADDR_TRANS
- bool
+ bool "RDMA/CM"
depends on INFINIBAND
default y
+ ---help---
+ Support for RDMA communication manager (CM).
+ This allows for a generic connection abstraction over RDMA.
config INFINIBAND_ADDR_TRANS_CONFIGFS
bool
--
2.17.0.484.g0c8726318c-goog
next prev parent reply other threads:[~2018-04-14 15:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 7:06 [PATCH] IB: make INFINIBAND_ADDR_TRANS configurable Greg Thelen
2018-04-13 12:47 ` Bart Van Assche
2018-04-13 17:27 ` [PATCH v2] " Greg Thelen
2018-04-14 15:13 ` Dennis Dalessandro
2018-04-14 15:34 ` Greg Thelen
2018-04-14 15:36 ` Greg Thelen [this message]
2018-04-14 18:22 ` [PATCH v3] " kbuild test robot
2018-04-14 18:22 ` kbuild test robot
2018-04-14 18:47 ` kbuild test robot
2018-04-14 18:47 ` kbuild test robot
2018-04-14 16:05 ` [PATCH v2] " Joe Perches
2018-04-16 9:03 ` [PATCH] " oulijun
2018-04-16 9:03 ` oulijun
2018-04-15 12:06 ` Christoph Hellwig
2018-04-16 4:02 ` Greg Thelen
2018-04-16 8:56 ` Christoph Hellwig
2018-04-16 14:51 ` 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=20180414153642.28178-1-gthelen@google.com \
--to=gthelen@google.com \
--cc=Bart.VanAssche@wdc.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tarick@google.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 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.