From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 0/2] two small cleanups
Date: Wed, 14 Dec 2022 18:38:21 +0100 [thread overview]
Message-ID: <0fe3ca2a-ada9-561b-8cac-ef32678dcda8@tessares.net> (raw)
In-Reply-To: <cover.1670575887.git.geliang.tang@suse.com>
Hi Geliang, Mat,
On 09/12/2022 09:57, Geliang Tang wrote:
> Two small cleanups.
>
> Geliang Tang (2):
> mptcp: use net instead of sock_net
> mptcp: use local variable ssk in write_options
Thank you for the patches and the reviews!
Now in our tree (feat. for net-next) with Mat's RvB tag:
New patches for t/upstream:
- 3f76289942fd: mptcp: use net instead of sock_net
- cd700ab87ddb: mptcp: use local variable ssk in write_options
- Results: 3f302724c1a3..652f1687a656 (export)
Tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20221214T173738
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
prev parent reply other threads:[~2022-12-14 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 8:57 [PATCH mptcp-next 0/2] two small cleanups Geliang Tang
2022-12-09 8:57 ` [PATCH mptcp-next 1/2] mptcp: use net instead of sock_net Geliang Tang
2022-12-09 8:57 ` [PATCH mptcp-next 2/2] mptcp: use local variable ssk in write_options Geliang Tang
2022-12-09 10:35 ` mptcp: use local variable ssk in write_options: Tests Results MPTCP CI
2022-12-13 23:31 ` MPTCP CI
2022-12-13 23:06 ` [PATCH mptcp-next 0/2] two small cleanups Mat Martineau
2022-12-14 17:38 ` Matthieu Baerts [this message]
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=0fe3ca2a-ada9-561b-8cac-ef32678dcda8@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/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.