From: Geliang Tang <geliangtang@gmail.com>
To: Matthieu Baerts <matttbe@kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Fwd: [PATCH iperf3] add MPTCPv1 support
Date: Wed, 6 Mar 2024 11:45:41 +0800 [thread overview]
Message-ID: <CA+WQbwuOGYVGmYGVtTNB4uLxH3B6HBuufQQku6rBKLoLACjZ2Q@mail.gmail.com> (raw)
In-Reply-To: <CA+WQbwsnoGTfwc1R1svxd7fVk7_b5+6ZdT7f=X7jkRkigmRp_A@mail.gmail.com>
---------- Forwarded message ---------
发件人： Geliang Tang <geliangtang@gmail.com>
Date: 2024年3月6日周三 11:42
Subject: Re: [PATCH iperf3] add MPTCPv1 support
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Geliang Tang <geliang.tang@suse.com>, <mptcp@lists.linux.dev>
Hi Matt,
>
> Hi Geliang,
>
> On 13/07/2023 09:03, Geliang Tang wrote:
> > On Wed, Jul 12, 2023 at 10:14:31AM +0200, Matthieu Baerts wrote:
> >> Hi Geliang,
> >>
> >> On 30/06/2023 18:03, Matthieu Baerts wrote:
> >>> Hi Geliang,
> >>>
> >>> Thank you for this, that would be helpful!
> >>>
> >>> The code looks good to me, I just have one suggestion for the commit
> >>> message, one "typo" with the alignment and one small suggestion in the
> >>> code. Please see below.
> >>>
> >>> I think you can create a new PR on esnet/iperf repo (and mention it
> >>> replaces the one of Paolo).
> >>
> >> What do you plan to do with this patch?
> >>
> >> There is no hurry at all to suggest it upstream (esnet/iperf) but it is
> >> mainly to know if you are expecting something from one of us, just to
> >> avoid a deadlock :)
> >
> > Hi Matt,
> >
> > Thanks for the review, a v2 will be sent later.
>
> Thank you, no hurry at all, take your time!
>
> If you prefer, you can also directly send the v2 to repo, up
> to you, I don't mind reviewing it before or after.
I sent out v2 to MPTCP ML and the iperf maintainer today. Sorry, v2
came too late. You can now update the status on patchwork.
Thanks,
-Geliang
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
>
prev parent reply other threads:[~2024-03-06 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 5:20 [PATCH iperf3] add MPTCPv1 support Geliang Tang
2023-06-30 16:03 ` Matthieu Baerts
2023-07-12 8:14 ` Matthieu Baerts
2023-07-13 7:03 ` Geliang Tang
2023-07-13 8:22 ` Matthieu Baerts
2024-03-06 3:42 ` Geliang Tang
2024-03-06 3:45 ` Geliang Tang [this message]
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=CA+WQbwuOGYVGmYGVtTNB4uLxH3B6HBuufQQku6rBKLoLACjZ2Q@mail.gmail.com \
--to=geliangtang@gmail.com \
--cc=matttbe@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).