On Tue, Jun 19, 2018 at 11:02:48AM -0500, Steve Wise wrote: > > > On 6/19/2018 12:40 AM, Christoph Hellwig wrote: > > On Mon, Jun 18, 2018 at 10:18:18AM -0500, Steve Wise wrote: > >> > >> On 6/18/2018 9:49 AM, Steve Wise wrote: > >>> Hey Christoph, will you merge patches 2 and 3 for -next? I think > >>> they're ready. I also have a nvmetcli patch I can send out for using > >>> param_inline_data_size. > >>> > >>> > >> Or I can rebase on 4.18-rc1 and resend... > > Yes, please do. I'd also like to see at least an ACK from one or our > > RDMA low level experts. > > > > Sure. > > +doug and jason. > > There is one merge issue: This series will require the max_send/recv_sge > commit, which is merged in rdma-next [1] just recently. Perhaps you can > pull that from the linux-rdma repo if and when these 2 nvme patches are > pulled into your repo? I think that will allow easy merging when the > block and rdma repos get merged into Linus' repo. Pulling the rdma tree into nvme is probably not something anyone would want to do.. Can we take these patches through rdma instead? Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
