[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170516.133644.850927380166261577.davem@davemloft.net>
Date: Tue, 16 May 2017 13:36:44 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: dledford@...hat.com
Cc: Bart.VanAssche@...disk.com, torvalds@...ux-foundation.org,
hch@....de, netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
stable@...r.kernel.org, ubraun@...ux.vnet.ibm.com
Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
From: Doug Ledford <dledford@...hat.com>
Date: Tue, 16 May 2017 13:20:44 -0400
> Anyway, we're just talking out what happened, when what we really need
> to focus on is moving forward. Again, your thoughts on marking SMC
> EXPERIMENTAL until it's fixed up and unfreezing the API in case we need
> to adjust it to work on different link layers?
Something like:
http://patchwork.ozlabs.org/patch/762803/
with the addition of the EXPERIMENTAL dependency?
Sure.
Powered by blists - more mailing lists