MPTCP Linux Development
 help / color / mirror / Atom feed
From: Tao Cui <cui.tao@linux.dev>
To: quanyeyang <quanyeyang@proton.me>, Matthieu Baerts <matttbe@kernel.org>
Cc: cui.tao@linux.dev, mptcp@lists.linux.dev, geliang@kernel.org,
	cuitao@kylinos.cn
Subject: Re: [PATCH mptcp-next 1/2] mptcp: pm: bound extra_subflows admission on userspace PM
Date: Thu, 3 Sep 2026 16:57:56 +0800	[thread overview]
Message-ID: <b898ed5f-702f-4b22-9af9-7f79b111ae77@linux.dev> (raw)
In-Reply-To: <U6pTh6EPoeSgwE2EHl9q6Urj4YiZFTfOINajSmMtooO9YzNmfQXdeB4pXt8P9Nh6FjtZrqjgs50Rlkxdm5Hyfgz65nUYNcmwmV76PVrTeUY=@proton.me>

Hi Quanye,

在 2026/9/3 11:42, quanyeyang 写道:
> Hi Matt, Tao,
> 
> On 02/09/2026 18:36, Matthieu Baerts wrote:
>> So, at the end, we can re-used the same version as Quanye. Would it be
>> OK for both of you to have a Co-developed-by tag here?
> 
> Fine with me. Please reuse `ret` and drop the comment in v2, with
> Co-developed-by tags for both of us.
> 
> On 02/09/2026 18:52, Matthieu Baerts wrote:
>> Maybe a goto could be used here ... to here, not to modify the rest
>> of the code?
>>
>> Would it be OK for both of you if this part of Quanye's patch is
>> added to Tao's v2 series with Quanye as author?
> 
> Also fine. Please take the Netlink extra_subflows cap in v2 with me
> as author, using a goto to the existing error cleanup instead of the
> else-wrapping I sent.
> 
> I will not send a competing series.
> 

Thanks for having a look at this too, and for making the
coordination easy.

You're right that the Netlink path was still open in my series,
good catch. I'll take your patch into the v2 series as we just
agreed, with you as author of that part.

Happy to share this one with you.

Thanks,
Tao

> Thanks,
> Quanye


  reply	other threads:[~2026-09-03  8:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  9:32 [PATCH mptcp-next 0/2] mptcp: pm: fix reachable extra_subflows guards Tao Cui
2026-08-31  9:32 ` [PATCH mptcp-next 1/2] mptcp: pm: bound extra_subflows admission on userspace PM Tao Cui
2026-09-02 16:39   ` Matthieu Baerts
2026-09-03  3:42     ` quanyeyang
2026-09-03  8:57       ` Tao Cui [this message]
2026-09-03  8:55     ` Tao Cui
2026-09-03  9:13       ` Matthieu Baerts
2026-08-31  9:32 ` [PATCH mptcp-next 2/2] mptcp: pm: skip extra_subflows accounting on disconnected msk Tao Cui
2026-08-31 10:11   ` sashiko-bot
2026-08-31 13:00     ` Tao Cui
2026-09-02 16:32       ` Matthieu Baerts
2026-09-02 16:56   ` Matthieu Baerts
2026-08-31 10:25 ` [PATCH mptcp-next 0/2] mptcp: pm: fix reachable extra_subflows guards MPTCP CI

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=b898ed5f-702f-4b22-9af9-7f79b111ae77@linux.dev \
    --to=cui.tao@linux.dev \
    --cc=cuitao@kylinos.cn \
    --cc=geliang@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=quanyeyang@proton.me \
    /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