MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net] Squash to "mptcp: update window_clamp on subflows when SO_RCVBUF is set"
Date: Fri, 15 May 2026 05:11:48 +0200	[thread overview]
Message-ID: <03428940-5fa7-41db-944d-86320b68ce66@kernel.org> (raw)
In-Reply-To: <20260515022332.55392-2-matttbe@kernel.org>

On 15/05/2026 04:23, Matthieu Baerts (NGI0) wrote:
> Remove the useless 'inline' keyword for a static function in a .c file.
> 
> Spot by NIPA when sending the patch.

No need to review this one, it is quite obvious. Just applied:

New patches for t/upstream-net and t/upstream:

- Results: abcff95a440d..abcff95a440d (export-net)
- Results: 564a2979a856..564a2979a856 (export)

Tests are now in progress:

- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/25fac03b8a5e5bba4941858547159f14d545d805/checks

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



  reply	other threads:[~2026-05-15  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  2:23 [PATCH mptcp-net] Squash to "mptcp: update window_clamp on subflows when SO_RCVBUF is set" Matthieu Baerts (NGI0)
2026-05-15  3:11 ` Matthieu Baerts [this message]
2026-05-15  3:19 ` 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=03428940-5fa7-41db-944d-86320b68ce66@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