From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: MPTCP patches pending for -net
Date: Thu, 28 Jul 2022 16:06:50 -0700 (PDT) [thread overview]
Message-ID: <73f44e58-3ead-e2fc-ac83-4e3ee99d534@linux.intel.com> (raw)
Hi Paolo -
Since we didn't get to discuss this question in the meeting today: With
the final -net pull request for 5.19-final already sent, should I wait
until next week to send the two patches we have in export-net now?
mptcp: do not queue data on closed subflows
mptcp: move subflow cleanup in mptcp_destroy_common()
Thanks,
--
Mat Martineau
Intel
next reply other threads:[~2022-07-28 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 23:06 Mat Martineau [this message]
2022-07-29 8:44 ` MPTCP patches pending for -net 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=73f44e58-3ead-e2fc-ac83-4e3ee99d534@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).