From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH 0/4] mptcp: some cleanups
Date: Mon, 11 Nov 2019 12:28:57 +0100 [thread overview]
Message-ID: <cover.1573471403.git.pabeni@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
This address the build issue we currently have on patch
"mptcp: Add key generation and token tree", plus move around some related
code for consistency.
No differences in the resulting code vs current git tree.
The tree should build on each patch now.
Paolo Abeni (1):
1/4 mptcp: drop most of mptcp_init_sock() impl
2/4 mptcp: use customary name for tcp_sock variable
3/4 mptcp: init ctx->icsk_af_ops in subflow_ulp_init()
4/4 mptcp: init new_ctx->icsk_af_ops() in subflow_ulp_clone()
net/mptcp/protocol.c | 13 +------------
1 file changed, 1 insertion(+), 12 deletions(-)
--
2.21.0
reply other threads:[~2019-11-11 11:28 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=cover.1573471403.git.pabeni@redhat.com \
--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.