From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next] mptcp: fix kdoc warnings
Date: Fri, 30 Jan 2026 11:25:16 +0100 [thread overview]
Message-ID: <a5b63ab2-5053-41f4-95bb-10252af9edae@kernel.org> (raw)
In-Reply-To: <186516ed4c548c2a35584153c5f995a205064725.camel@kernel.org>
Hi Geliang,
On 30/01/2026 09:28, Geliang Tang wrote:
> On Fri, 2026-01-30 at 08:52 +0100, Matthieu Baerts (NGI0) wrote:
>> The following warnings were visible:
(...)
>> Address all of them: either by using the 'Return:' keyword, or by
>> adding
>> a missing initial short description.
>>
>> The MPTCP CI will soon report issues with kdoc to avoid introducing
>> new
>> issues and being flagged by the Netdev CI.
>>
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
> Looks good to me.
Thank you for the review!
Note that the CI now checks these warnings, e.g.:
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/21509881177
Now in our tree:
New patches for t/upstream:
- 3d0ed4124117: mptcp: fix kdoc warnings
- Results: 803afbaeada9..50e7f60d4f2a (export)
Tests are now in progress:
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/9538a224bbca2b776a98b1384c7b8b0156e5dc89/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-01-30 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 7:52 [PATCH mptcp-next] mptcp: fix kdoc warnings Matthieu Baerts (NGI0)
2026-01-30 8:28 ` Geliang Tang
2026-01-30 10:25 ` Matthieu Baerts [this message]
2026-01-30 9:26 ` MPTCP CI
2026-01-30 9:59 ` 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=a5b63ab2-5053-41f4-95bb-10252af9edae@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@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