Comment 7 for bug 1971027

@huzhiming100 IMHO the best would be setup a public git repository based on our latest kinetic:linux kernel (https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic).

Then you can periodically apply and push new versions of these patch sets there and ping us (here or by sending an email to our kernel mailing list <email address hidden>) when new versions are available. And ideally the commits should have a reference to the upstream email thread or a reference to an upstream git repository (once they are accepted upstream).

In this way we can easily monitor the progress of these patch sets and respond quickly with our review.

Regarding the code itself ideally we would like to receive patch sets in a more "stable" state, meaning that at least patches have been Acked-by some upstream maintainers. In this way we don't expect to see big changes in the kernel ABI or big code refactoring that would make our maintenance a little problematic.

I think all of the above would strongly speed up the process of getting these two patch set applied to our Ubuntu kernels.

And if you have any doubt or something that I wrote is not clear feel free to ask any question.

Thanks!