On 9/25/16 1:39 AM, Amrani, Ram wrote: > Hi Doug, > We will release qedr RFC v3 this week that will address all of the comments received on v1 and v2. Following this RFC we would like to generate a patch series. > Note that the RFC contains patches to qed and qede that are maintained in netdev so the submission may be affected by netdev activity. > Currently the RFC is based on netdev's net-next but we can rebase against your git (git://github.com/dledford/linux.git). > > What guidelines should we follow with this submission? > What is the time frame to make it into kernel 4.9? There are currently 5 (5!!!) entirely new drivers that people want to get merged. Reviewing those monstrous beasts is a nightmare. The chances that I will get to yours for 4.9 are slim at best. However, on the off chance that I might get to it, base the qed patches against Dave's net-next (up until the merge window opens, then base it on his net tree as that's what will get merged). The qedr patches should be based on my current k.o/for-4.9 branch off of k.o. When you submit any patches, I would suggest doing it in two separate submissions (if possible). One that is just the preparatory qed patches. They should be sent to netdev@ and linux-rdma@. The submission should note that they are intended to be taken with the qedr driver. If netdev@ reviews/acks the series, then Dave can let me know if he wants me to take the series and keep with with the remaining qedr series, or if he wants to take them himself and I just make sure my pull request of the qedr patches goes to Linus after his. The second set would obviously be the new qedr driver. It need not go to netdev. Once it's here, then it's a matter of the netdev@ people signing off on the qed series changes, me signing off on the qedr changes, then it can go in. -- Doug Ledford <dledford@xxxxxxxxxx> GPG Key ID: 0E572FDD Red Hat, Inc. 100 E. Davie St Raleigh, NC 27601 USA
Attachment:
signature.asc
Description: OpenPGP digital signature
