On Thu, Nov 02, 2017 at 06:31:25PM +0200, Leon Romanovsky wrote: > > Header file patch, man pages, documentation and an example are the > > logical next steps to vet a proposed verbs API in the public forum. > > And I think that RFC should be much lighter than you wrote. Pseudo API, > motivation and examples. The general rule in the kernel community is that things do not get reviewed without code, and as I said, this specific RFC is confusing, to say the least. So if you want some kind of ack that the idea will not be revised when the code is presented, you need to at least present some code to get it reviewed. In this case, man pages and header files would be a reasonable place to start. This is particularly true since none of these new RFCs are not backed by any sort of spec, and the code submission and RFC itself forms the spec. Starting by writing the spec is a sane engineering practice. 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
