From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Patches ready for net-next
Date: Mon, 2 Aug 2021 16:38:05 -0700 (PDT) [thread overview]
Message-ID: <d015d3be-ca34-56bb-4a85-1660fcc13bb5@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Hi Paolo -
On Thursday we talked about patches to send next:
Patches to send to netdev:
- net-next:
- 2 series are ready:
- Paolo's series (backup / scheduler):
→ maybe best to wait, see issues/219
- Yonglong & Geliang's series (ADD_ADDR/RM_ADDR refactor)
I saw your comment on
https://github.com/multipath-tcp/mptcp_net-next/issues/219, you mentioned
that the two newest patches on the export branch looked like they were not
related to the divide error seen by syzkaller. Any reason to wait on
sending the active-backup series earlier in the export branch:
9058115c3ff7 selftests: mptcp: add testcase for active-back
8a8c8b5711d7 mptcp: backup flag from incoming MPJ ack option
1f05f7524500 mptcp: add mibs for stale subflows processing
f1abc22dbc32 mptcp: faster active backup recovery
69a226d4b8c4 mptcp: cleanup sysctl data and helpers
f0699e78732e mptcp: handle pending data on closed subflow
167e8cf026aa mptcp: less aggressive retransmission strategy
77477273b6de mptcp: more accurate timeout
?
Thanks,
--
Mat Martineau
Intel
reply other threads:[~2021-08-02 23:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d015d3be-ca34-56bb-4a85-1660fcc13bb5@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--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 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.