From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: Additional part 3 squash suggestion
Date: Fri, 20 Mar 2020 00:34:17 +0100 [thread overview]
Message-ID: <20200319233417.GA3305@breakpoint.cc> (raw)
In-Reply-To: alpine.OSX.2.22.394.2003191614420.3820@sugandh1-mobl2.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
Mat Martineau <mathew.j.martineau(a)linux.intel.com> wrote:
>
> Florian and Matthieu -
>
> From the meeting notes, it looks like "subflow: place further subflows on
> new 'join_list'" is the commit that you're planning to squash.
>
> What do you think about also squashing "mptcp: increment MIB counters in a
> few places" in to the previous MIB commit? Seems like our patch count for
> part 3 is still kind of high.
SGTM. We could change the commit title as follows:
- mptcp: add MIB counter infrastructure
+ mptcp: add and use MIB counter infrastructure
and toss the commit description of the 'increment MIB' patch,
it doesn't add any value.
next reply other threads:[~2020-03-19 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 23:34 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-20 1:09 [MPTCP] Re: Additional part 3 squash suggestion Paolo Abeni
2020-03-20 16:20 Matthieu Baerts
2020-03-23 17:07 Matthieu Baerts
2020-03-23 19:34 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=20200319233417.GA3305@breakpoint.cc \
--to=unknown@example.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 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.