All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: Greg Thelen <gthelen@google.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,
	Tarick Bedeir <tarick@google.com>
Subject: Re: [PATCH v2] IB: make INFINIBAND_ADDR_TRANS configurable
Date: Sat, 14 Apr 2018 11:13:00 -0400	[thread overview]
Message-ID: <b1f20a68-2ed4-935f-4a9c-8a28c142ceee@intel.com> (raw)
In-Reply-To: <20180413172708.30286-1-gthelen@google.com>

On 4/13/2018 1:27 PM, Greg Thelen wrote:
> Allow INFINIBAND without INFINIBAND_ADDR_TRANS.
> 
> Signed-off-by: Greg Thelen <gthelen@google.com>
> Cc: Tarick Bedeir <tarick@google.com>
> Change-Id: I6fbbf8a432e467710fa65e4904b7d61880b914e5

Forgot to remove the Gerrit thing.

-Denny

  reply	other threads:[~2018-04-14 15:13 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 [this message]
2018-04-14 15:34       ` Greg Thelen
2018-04-14 15:36         ` [PATCH v3] " Greg Thelen
2018-04-14 18:22           ` 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=b1f20a68-2ed4-935f-4a9c-8a28c142ceee@intel.com \
    --to=dennis.dalessandro@intel.com \
    --cc=Bart.VanAssche@wdc.com \
    --cc=dledford@redhat.com \
    --cc=gthelen@google.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.