On 16/02/20 07:57, James Hogan wrote: >> We are in the process of handling this within the company, and this >> patch should go via MIPS tree, not trivial tree - will be updated when >> the opinions are crystallized, and all consultations with others were >> done. There is no rush. > Hi Aleksandar, > > I respectfully disagree. In the mean time I am still listed as > maintainer even though this patch has reflected reality for more than 18 > months since the 2018 closure of the MIPS UK offices. > > If "the company" wish to eventually crystalize their opinion and assign > someone else this role (which they've had at least 6 weeks to do even > since I sent the patch) they can always submit a new patch. > > In the mean time I'd appreciate if somebody could take the patch ASAP.
I agree with James, the situation has already crystallized long before the opinions will have. You have done excellent work on the TCG side, but neither the kernel nor the QEMU side of KVM have seen any significant activity. If your employer becomes more interested in KVM then the status can be changed. I think it's okay if we delay the patch a couple weeks more (which is more or less when Laurent or I will send the next pull request), but certainly not past 5.0 soft freeze. Thanks, Paolo
