From: dledford@redhat.com (Doug Ledford)
Subject: [PATCH 0/6] IB: make INFINIBAND_ADDR_TRANS configurable
Date: Fri, 27 Apr 2018 12:07:52 -0400 [thread overview]
Message-ID: <1524845272.11756.51.camel@redhat.com> (raw)
In-Reply-To: <20180426181935.32977-1-gthelen@google.com>
On Thu, 2018-04-26@11:19 -0700, Greg Thelen wrote:
> This series allows for CONFIG_INFINIBAND without
> CONFIG_INFINIBAND_ADDR_TRANS (aka RDMA communication manager).
> Fuzzing has been finding fair number of CM bugs.
> So provide an option to disable it in systems which don't need it.
>
> Changes since last posting (https://lkml.org/lkml/2018/4/25/1266):
> - added ("ib_srp: depend on INFINIBAND_ADDR_TRANS") patch
[ snip explanation of series ]
Thanks for taking the time to research this out. Series applied.
--
Doug Ledford <dledford at redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20180427/e919981f/attachment.sig>
prev parent reply other threads:[~2018-04-27 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 18:19 [PATCH 0/6] IB: make INFINIBAND_ADDR_TRANS configurable 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
2018-04-27 16:07 ` Doug Ledford [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=1524845272.11756.51.camel@redhat.com \
--to=dledford@redhat.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