On 06/17/2014 10:59 PM, Akemi Yagi wrote:
On Tue, Jun 17, 2014 at 12:51 PM, Guillaume Derval guillaume.derval@student.uclouvain.be wrote:
Le 17 juin 2014 à 19:57, Akemi Yagi amyagi@gmail.com a écrit :
With my initial concern gone, I now have more practical question.
The modifications are quite extensive as noted in the beginning. I count 15 patches in include/ and 29 in /net . For each kernel update, the patch set must be updated/tested. Also there may be updates to the patches themselves within a given kernel release. How can this be best handled? Could dealing with the patches cause a delay in the cplus kernel release?
Having a separate kernel addressing the mptcp stuff might work around that potential issue.
Akemi
I personally think that creating a separate kernel (kernel-cplus-mptcp? :-) ) is the best thing to do.
Best regards, Guillaume Derval.
That probably makes everyone's life easier. And KB says he would provide support either way. In this case, it will be a distro kernel derivative, so a 'kernel-mptcp' ?
+1 for separate kernel-mptcp