From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH v3 0/6] mptcp: update mptcp ack sequence from work queue
Date: Thu, 20 Feb 2020 15:34:19 +0100 [thread overview]
Message-ID: <20200220143426.28626-1-fw@strlen.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
V3. No changes since v2, I only updated commit messages in
patches 1, 2, 3 and 6.
I think we should try to avoid needless squashing and keep
these as-is for now. We can always condense some of this later
on in case we need to reduce number of individual patches for some
reason.
next reply other threads:[~2020-02-20 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 14:34 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-18 12:21 [MPTCP] [PATCH v3 0/6] mptcp: update mptcp ack sequence from work queue Florian Westphal
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=20200220143426.28626-1-fw@strlen.de \
--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.