* [MPTCP] [PATCH 0/7] Minor patches
@ 2019-06-06 0:36 Peter Krystad
0 siblings, 0 replies; 2+ messages in thread
From: Peter Krystad @ 2019-06-06 0:36 UTC (permalink / raw)
To: mptcp
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
Mostly responding to some of Paolo's comments on the MP_JOIN RFC.
Peter Krystad (7):
mptcp: reduce number of pr_debug() calls.
mptcp: reduce number of pr_debug() calls.
mptcp: reduce number of pr_debug() calls.
mptcp: reduce number of pr_debug() calls.
mptcp: parsing DSS option should use own flags field.
mptcp: Check flags in MP_CAPABLE option
mptcp: Refactor mptcp_established_options() to single hook
include/linux/tcp.h | 1 +
include/net/mptcp.h | 30 +++-----------
net/ipv4/tcp_output.c | 21 +++-------
net/mptcp/options.c | 95 ++++++++++++++++++++++++++++---------------
net/mptcp/protocol.c | 9 +---
net/mptcp/protocol.h | 15 +++++--
net/mptcp/subflow.c | 5 +--
7 files changed, 91 insertions(+), 85 deletions(-)
--
2.17.2
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [MPTCP] [PATCH 0/7] Minor patches
@ 2019-06-07 11:24 Matthieu Baerts
0 siblings, 0 replies; 2+ messages in thread
From: Matthieu Baerts @ 2019-06-07 11:24 UTC (permalink / raw)
To: mptcp
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
Hi Peter,
On 06/06/2019 02:36, Peter Krystad wrote:
> Mostly responding to some of Paolo's comments on the MP_JOIN RFC.
>
> Peter Krystad (7):
> mptcp: reduce number of pr_debug() calls.
> mptcp: reduce number of pr_debug() calls.
> mptcp: reduce number of pr_debug() calls.
> mptcp: reduce number of pr_debug() calls.
> mptcp: parsing DSS option should use own flags field.
> mptcp: Check flags in MP_CAPABLE option
> mptcp: Refactor mptcp_established_options() to single hook
Thank you for this patch-set!
As agreed yesterday at the meeting, I added patches 2 → 6 in the repo.
Please note that the first patch was also doing some refactoring that
were affecting the 6th patch ("mptcp: Check flags in MP_CAPABLE
option"). For more details about that, please see the corresponding email.
When you will send a v2 for the first and last patch, may you do a
rebase and also apply the refactoring in the code changed by the 6th
patch? Anyway I guess you should get a small and simple conflict when
doing the rebase.
Cheers,
Matt
--
Matthieu Baerts | R&D Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-07 11:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-06 0:36 [MPTCP] [PATCH 0/7] Minor patches Peter Krystad
-- strict thread matches above, loose matches on Subject: below --
2019-06-07 11:24 Matthieu Baerts
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.