From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v2 0/7] some cleanups
Date: Tue, 27 Feb 2024 10:12:04 +0100 [thread overview]
Message-ID: <596a49bf-7d1d-4f44-97ba-c189522c7d7a@kernel.org> (raw)
In-Reply-To: <cover.1708588977.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 22/02/2024 09:03, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v2:
> - address Matt's comments in v1
>
> Geliang Tang (7):
> mptcp: make pm_remove_addrs_and_subflows static
> mptcp: drop duplicate header inclusions
> mptcp: update set_flags interfaces
> mptcp: set error messages for set_flags
> mptcp: drop lookup_by_id in lookup_addr
Thank you for the patches! I just applied these 5 patches in our tree
(feat. for net-next):
New patches for t/upstream:
- eb5a7de62ab0: mptcp: make pm_remove_addrs_and_subflows static
- f2d06a42d2cc: mptcp: drop duplicate header inclusions
- 6df3b1d4a5a9: mptcp: update set_flags interfaces
- 5cf3d6085921: mptcp: set error messages for set_flags
- 789aaac60f7f: mptcp: drop lookup_by_id in lookup_addr
- Results: 425c5fffb4c5..ace42d7d3a0f (export)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-02-27 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 8:03 [PATCH mptcp-next v2 0/7] some cleanups Geliang Tang
2024-02-22 8:03 ` [PATCH mptcp-next v2 1/7] mptcp: make pm_remove_addrs_and_subflows static Geliang Tang
2024-02-22 8:03 ` [PATCH mptcp-next v2 2/7] mptcp: drop duplicate header inclusions Geliang Tang
2024-02-22 8:03 ` [PATCH mptcp-next v2 3/7] mptcp: update set_flags interfaces Geliang Tang
2024-02-22 8:03 ` [PATCH mptcp-next v2 4/7] mptcp: set error messages for set_flags Geliang Tang
2024-02-22 8:03 ` [PATCH mptcp-next v2 5/7] mptcp: drop lookup_by_id in lookup_addr Geliang Tang
2024-02-22 8:03 ` [PATCH mptcp-next v2 6/7] mptcp: add check_id for lookup_anno_list_by_saddr Geliang Tang
2024-02-26 10:07 ` Matthieu Baerts
2024-03-28 18:27 ` Matthieu Baerts
2024-03-29 4:50 ` Geliang Tang
2024-02-22 8:03 ` [PATCH mptcp-next v2 7/7] selftests: mptcp: flush userspace addrs list Geliang Tang
2024-02-22 8:51 ` selftests: mptcp: flush userspace addrs list: Tests Results MPTCP CI
2024-02-26 10:07 ` [PATCH mptcp-next v2 7/7] selftests: mptcp: flush userspace addrs list Matthieu Baerts
2024-02-26 10:06 ` [PATCH mptcp-next v2 0/7] some cleanups Matthieu Baerts
2024-02-27 1:40 ` Geliang Tang
2024-02-27 9:11 ` Matthieu Baerts
2024-02-27 9:12 ` 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=596a49bf-7d1d-4f44-97ba-c189522c7d7a@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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