LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "tarick@google.com" <tarick@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
"axboe@fb.com" <axboe@fb.com>,
"gthelen@google.com" <gthelen@google.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"sfrench@samba.org" <sfrench@samba.org>,
"keith.busch@intel.com" <keith.busch@intel.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"dledford@redhat.com" <dledford@redhat.com>
Subject: Re: [PATCH 6/6] IB: make INFINIBAND_ADDR_TRANS configurable
Date: Thu, 26 Apr 2018 18:26:24 +0000 [thread overview]
Message-ID: <cdbccbcb15ed155243149a6ec3ee540df523990c.camel@wdc.com> (raw)
In-Reply-To: <20180426181935.32977-7-gthelen@google.com>
On Thu, 2018-04-26 at 11:19 -0700, Greg Thelen wrote:
> Allow INFINIBAND without INFINIBAND_ADDR_TRANS because fuzzing has been
> finding fair number of CM bugs. So provide option to disable it.
Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>
next prev parent reply other threads:[~2018-04-26 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 18:19 [PATCH 0/6] " Greg Thelen
2018-04-26 18:19 ` [PATCH 1/6] nvme: depend on INFINIBAND_ADDR_TRANS Greg Thelen
2018-04-26 18:19 ` [PATCH 2/6] nvmet-rdma: " Greg Thelen
2018-04-26 18:19 ` [PATCH 3/6] ib_srpt: " Greg Thelen
2018-04-26 18:25 ` Bart Van Assche
2018-04-26 18:19 ` [PATCH 4/6] cifs: smbd: " Greg Thelen
2018-04-26 18:19 ` [PATCH 5/6] ib_srp: " Greg Thelen
2018-04-26 18:25 ` Bart Van Assche
2018-04-26 18:19 ` [PATCH 6/6] IB: make INFINIBAND_ADDR_TRANS configurable Greg Thelen
2018-04-26 18:26 ` Bart Van Assche [this message]
2018-04-27 16:07 ` [PATCH 0/6] " Doug Ledford
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=cdbccbcb15ed155243149a6ec3ee540df523990c.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@fb.com \
--cc=dledford@redhat.com \
--cc=gthelen@google.com \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=keith.busch@intel.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=sfrench@samba.org \
--cc=tarick@google.com \
--subject='Re: [PATCH 6/6] IB: make INFINIBAND_ADDR_TRANS configurable' \
/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
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).