From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] some squashing needed?
Date: Fri, 27 Sep 2019 23:11:11 +0200 [thread overview]
Message-ID: <20190927211111.GI9938@breakpoint.cc> (raw)
In-Reply-To: 0290621d-11de-6515-baf9-429ed9582783@tessares.net
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> On 27/09/2019 17:51, Florian Westphal wrote:
> > I can fold Peters mptcp prefix patch for crypto where needed and push a
> > v2, let me know.
>
> I just pushed a new tree on mptcp_net-next repo on Github based on your
> branch :)
Awesome.
> I didn't want to block anybody but I can re-create a new one again later
> if needed!
Great.
> Also I don't mind squashing this patch and also do the same for the
> remaining functions (subflow_ ones I guess). I can do that on Monday if
> it is OK for you.
Sure.
I squashed Peters patch, you can get a branch with it folded by pulling
git://git.breakpoint.cc/fw/mptcp-next.git export_squash_11
The diff between current export and this branch is Peters patch, nothing
else.
If you could prefix the path management api that would be great (to avoid
confusion with 'power management') subflow would be good too.
> Also, before recreating the new tree, I remove all (Git) refs to the
> previous ones. If someone uses our repo with Topgit (we never know :) ),
> please do the same on your side!
Sorry, not following. What would you like me to do?
I plan to work on a v2 of the snmp counters on Monday, esp. dropping all
the unused/dubious counters.
If there is anything else please let me know.
I still need to do v2 of the 'poll' patch set, I will do that next after
the snmp counters are done.
Thanks,
Florian
next reply other threads:[~2019-09-27 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:11 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-27 15:59 [MPTCP] some squashing needed? Matthieu Baerts
2019-09-27 15:51 Florian Westphal
2019-09-27 15:02 Matthieu Baerts
2019-09-26 17:20 Paolo Abeni
2019-09-26 15:05 Florian Westphal
2019-09-25 17:01 Matthieu Baerts
2019-09-25 16:45 Paolo Abeni
2019-09-23 12:03 Matthieu Baerts
2019-09-23 11:41 Paolo Abeni
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=20190927211111.GI9938@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.