From: Paolo Abeni <pabeni@redhat.com>
To: "吴玑震 (Jeason Wu)" <jeason.wu@unisoc.com>
Cc: "任启凤 (Serena Ren)" <Serena.Ren@unisoc.com>, mptcp@lists.linux.dev
Subject: Re: Ask about MPTCP development progress and MPTCP in Kernel 5.4 GKI
Date: Mon, 3 May 2021 10:32:02 +0200 [thread overview]
Message-ID: <CAF6piCLgdRdzZ37ng1ycGB+TEfstTL58yqZa2ANFUZCdPj1=-A@mail.gmail.com> (raw)
In-Reply-To: <199d0f80d00540b5861a51b5baf27363@shmbx05.spreadtrum.com>
Hello,
First thing first, please use the mptcp devel mailing list
(mptcp@lists.linux.dev) for this kind of questions. I added the
relevant email address in CC.
On Sun, Apr 25, 2021 at 9:47 AM 吴玑震 (Jeason Wu) <jeason.wu@unisoc.com> wrote:
> 1. Is there a timeline for the release of the next MPTCP version? About when?
MPTCP development is tracked publicly via:
https://github.com/multipath-tcp/mptcp_net-next/projects/
https://github.com/multipath-tcp/mptcp_net-next/issues/
> 2. The MPTCP source code on GitHub is ported to Kernel5.4, and several parts will be modified to the original structure, which will cause GKI to fail. Is there any solution to this problem? Does the MPTCP team consider asking Google to make some changes on Kernel5.4 to better pass the GKI detection so that more users can use MPTCP?
The out of tree MPTCP implementation hosted by mptcp.org has separated
development. If there are any interoperability issues between the
official Linux implementation and the out-of-tree one, please file an
issue on:
https://github.com/multipath-tcp/mptcp_net-next/issues/
Please note that google has not direct governance on the Linux kernel.
Google, as many others, contribute to its development. Major changes
are discussed and agreed on the relevant ML or if possible at
conferences.
It's not clear to me what are the 'GKI' failures you refer to. As said
if you observe some bugs please file an issue and report as much
technical info as possible.
Cheers,
Paolo
parent reply other threads:[~2021-05-03 8:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <199d0f80d00540b5861a51b5baf27363@shmbx05.spreadtrum.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF6piCLgdRdzZ37ng1ycGB+TEfstTL58yqZa2ANFUZCdPj1=-A@mail.gmail.com' \
--to=pabeni@redhat.com \
--cc=Serena.Ren@unisoc.com \
--cc=jeason.wu@unisoc.com \
--cc=mptcp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.