> On Tue, Mar 13, 2018 at 04:56:39PM -0500, Steve Wise wrote: > > > On Tue, Mar 13, 2018 at 12:21:16PM -0500, Steve Wise wrote: > > > > > > > I guess an alternative is to submit the cxgb4 changes this cycle, > > > > and the iw_cxgb4 changes after those patches land in rdma-next > > > > (4.17-rc1 I assume). But this results in 2 release cycles to get > > > > the feature in, which is not ideal. (just thinking through the > > > > possibilities)... > > > > > > Yes. That is probably faster than you waiting to get a k.o account > > > though. > > > > Then chelsio should just submit the cxgb4 changes this cycle via netdev. > > Raju, you'll need to do that going forward. > > If that is the dependency order, then yes.. Another possibility is to push this series through one maintainer's repo. For example linux-rdma for this srq series. Then, for the rest of this cycle, all subsequent cxgb4 and iw_cxgb4 changes that depend on this series, flows through the same maintainer's repo until merged into Linus' tree. The key would be getting buy in from both maintainers, and making sure all maintainers ACK each series. Steve. -- 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
