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/2] Squash to "implement mptcp read_sock" v9
Date: Mon, 1 Sep 2025 12:22:19 +0200 [thread overview]
Message-ID: <64fce482-7dc7-4643-a73c-7491522f8589@kernel.org> (raw)
In-Reply-To: <cover.1756458375.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 29/08/2025 11:10, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v2:
> - a new squash-to patch for "mptcp: implement .read_sock".
When the series is a few days old, and has not been reviewed yet, I
think it is easier if you send a new version instead of squash-to patches.
I think such squash-to patches are good when patches have already been
applied, or when you realised you forgot something minor just after
having send a series with a few patches. (For the latter, it might be
interesting to use '--in-reply-to $PREVIOUS_COVER_LETTER'.)
When the v10 will be posted, I can check with Paolo if he is planning to
continue the review of this series.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2025-09-01 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 9:10 [PATCH mptcp-next v2 0/2] Squash to "implement mptcp read_sock" v9 Geliang Tang
2025-08-29 9:10 ` [PATCH mptcp-next v2 1/2] Squash to "mptcp: implement .read_sock" Geliang Tang
2025-08-29 9:10 ` [PATCH mptcp-next v2 2/2] Squash to "selftests: mptcp: connect: cover splice mode" Geliang Tang
2025-08-29 11:16 ` [PATCH mptcp-next v2 0/2] Squash to "implement mptcp read_sock" v9 MPTCP CI
2025-09-01 10:22 ` 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=64fce482-7dc7-4643-a73c-7491522f8589@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 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.