From: Matthieu Baerts <matttbe@kernel.org>
To: Davide Caratti <dcaratti@redhat.com>,
Mat Martineau <martineau@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] mptcp: refer to 'MPTCP' socket in comments
Date: Thu, 16 May 2024 10:23:05 +0200 [thread overview]
Message-ID: <93ccc9b4-fc0c-442f-a47e-5caa45cfd5ea@kernel.org> (raw)
In-Reply-To: <829272fc031f542c7a3d8e446eba19ee0f78dffb.1715794371.git.dcaratti@redhat.com>
Hi Davide,
On 15/05/2024 19:34, Davide Caratti wrote:
> we used to call it 'master' socket at the early stages of MPTCP
> development, but the correct wording is 'MPTCP' socket opposed to 'TCP
> subflows': convert the last 3 coments to use a more appropriate term.
Thanks! I'm giving my green light for that one (anyway, it cannot be
red, black, yellow or white... so green it is!)
Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-05-16 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 17:34 [PATCH mptcp-next] mptcp: refer to 'MPTCP' socket in comments Davide Caratti
2024-05-15 18:32 ` MPTCP CI
2024-05-16 8:23 ` Matthieu Baerts [this message]
2024-05-16 8:27 ` Matthieu Baerts
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=93ccc9b4-fc0c-442f-a47e-5caa45cfd5ea@kernel.org \
--to=matttbe@kernel.org \
--cc=dcaratti@redhat.com \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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