MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Gang Yan <gang.yan@linux.dev>, mptcp@lists.linux.dev
Cc: Gang Yan <yangang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v3] Squash-to "mptcp: pm: init and release mptcp_pm_ops"
Date: Mon, 6 Jul 2026 16:33:22 +0200	[thread overview]
Message-ID: <0b5f1978-4762-455f-a776-1fa991085d16@kernel.org> (raw)
In-Reply-To: <20260702063002.127027-1-gang.yan@linux.dev>

Hi Gang, Geliang,

On 02/07/2026 08:30, Gang Yan wrote:
> From: Gang Yan <yangang@kylinos.cn>
> 
> This patch removes the need to handle a NULL pm_ops in the fallback
> path, and moves the rcu_read_lock\unlock into mptcp_pm_ops_init.
> 
> Following sashiko's comments, it also moves the pr_debug() before
> bpf_module_put() in mptcp_pm_ops_release.

Thank you for the v3, and the review!

Now in our tree:

New patches for t/upstream:
- 7d1ab340593f: "squashed" in "mptcp: pm: init and release mptcp_pm_ops"
- e7a8a2a1215d: "Signed-off-by" + "Co-developed-by"
- Results: 653c410fe0bb..3c824013edcf (export)

Tests are now in progress:

- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/00c0b1f484bfd2a20ad6bf70f19a812a38d6922e/checks


Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      parent reply	other threads:[~2026-07-06 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  6:30 [PATCH mptcp-next v3] Squash-to "mptcp: pm: init and release mptcp_pm_ops" Gang Yan
2026-07-02  7:35 ` MPTCP CI
2026-07-03  1:13 ` Geliang Tang
2026-07-06 14:33 ` 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=0b5f1978-4762-455f-a776-1fa991085d16@kernel.org \
    --to=matttbe@kernel.org \
    --cc=gang.yan@linux.dev \
    --cc=mptcp@lists.linux.dev \
    --cc=yangang@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