On Fri, Jan 12, 2018 at 05:06:02PM +0200, Leon Romanovsky wrote: > On Fri, Jan 12, 2018 at 08:15:24AM -0600, Chien Tin Tung wrote: > > On Fri, Jan 12, 2018 at 07:58:38AM +0200, Leon Romanovsky wrote: > > > Hi, > > > > > > There is small set of fixes targeted for rdma-rc. > > > > For RC? Are these fixing regressions? We are already in RC7. > > Jason was clear last time, he wants to work like Dave, fixes go always > without any relation to -RC. I won't claim to know Dave's process since I don't drectly submit patches to Netdev. However given Dave's history with the kernel, I highly doubt he would accept patches late in RC cycle that would jeopardize a kernel release. I would like to hear directly from Doug and Jason on this and so we are clear on the policy to be enforced with infiniband subsystem. In the meantime, I will quote the official documentation from kernel.org (https://www.kernel.org/doc/html/v4.10/process/howto.html) 4.x kernel tree [...] After two weeks a -rc1 kernel is released and the focus is on making the new kernel as rock solid as possible. Most of the patches at this point should fix a regression. Bugs that have always existed are not regressions, so only push these kinds of fixes if they are important. Please note that a whole new driver (or filesystem) might be accepted after -rc1 because there is no risk of causing regressions with such a change as long as the change is self-contained and does not affect areas outside of the code that is being added. git can be used to send patches to Linus after -rc1 is released, but the patches need to also be sent to a public mailing list for review. Chien -- 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
