public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next] Squash to "mptcp: fix kdoc warnings"
Date: Thu, 5 Feb 2026 12:26:40 +0100	[thread overview]
Message-ID: <a961fe9d-c262-424e-bca4-a43aee4ef3a5@kernel.org> (raw)
In-Reply-To: <20260205-mptcp-fix-kdoc-yml-v1-1-9858c4b7baf6@kernel.org>

Hello,

On 05/02/2026 12:14, Matthieu Baerts (NGI0) wrote:
> include/uapi/linux/mptcp_pm.h is an auto-generated tool using
> Documentation/netlink/specs/mptcp_pm.yaml. So both files need to be
> modified.

No need to review this I think. I just applied it in our tree:

New patches for t/upstream:
- c5646ef8ae55: Squash to "mptcp: fix kdoc warnings"
- Results: a1fbe7e45597..073024280a58 (export)

Tests are now in progress:

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

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


  reply	other threads:[~2026-02-05 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 11:14 [PATCH mptcp-next] Squash to "mptcp: fix kdoc warnings" Matthieu Baerts (NGI0)
2026-02-05 11:26 ` Matthieu Baerts [this message]
2026-02-05 12:49 ` 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=a961fe9d-c262-424e-bca4-a43aee4ef3a5@kernel.org \
    --to=matttbe@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox