From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: Mat Martineau <martineau@kernel.org>
Subject: Re: [PATCH mptcp-next v2 0/3] doc: introduce MPTCP global doc
Date: Sun, 19 May 2024 10:56:44 +0200 [thread overview]
Message-ID: <d8ca6709-33b7-4db3-b258-09498eb0c9d1@kernel.org> (raw)
In-Reply-To: <20240518-mptcp-doc-v2-0-68304a17cd7d@kernel.org>
Hello,
On 18/05/2024 17:52, Matthieu Baerts (NGI0) wrote:
> The most interesting bit is in the last patch: a new 'mptcp' page in
> 'networking' documentation.
>
> The first patch is a fix (missing sysctl entry), and the second one
> reorder the sysctl entries.
I just applied this v2 in our tree.
I guess there is no need to wait before sending them upstream, so we can
have some reviews from the Doc team.
New patches for t/upstream-net and t/upstream:
- a2f67e9be84c: doc: mptcp: add missing 'available_schedulers' entry
- b720ebf6d555: doc: mptcp: alphabetical order
- 01721919a84a: doc: new 'mptcp' page in 'networking'
- Results: 7ff2cd284fdf..ef872e5e6e1a (export-net)
- Results: 2ccd59d4df6a..e7a4c0868f83 (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/7f7f9dac2795d5224e357b5646c83c63cd9add2c/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/61b1ea718087c5d099db254c2da376e3a566a93a/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-05-19 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 15:52 [PATCH mptcp-next v2 0/3] doc: introduce MPTCP global doc Matthieu Baerts (NGI0)
2024-05-18 15:52 ` [PATCH mptcp-next v2 1/3] doc: mptcp: add missing 'available_schedulers' entry Matthieu Baerts (NGI0)
2024-05-18 15:52 ` [PATCH mptcp-next v2 2/3] doc: mptcp: alphabetical order Matthieu Baerts (NGI0)
2024-05-18 15:52 ` [PATCH mptcp-next v2 3/3] doc: new 'mptcp' page in 'networking' Matthieu Baerts (NGI0)
2024-05-18 16:39 ` [PATCH mptcp-next v2 0/3] doc: introduce MPTCP global doc MPTCP CI
2024-05-19 8:56 ` 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=d8ca6709-33b7-4db3-b258-09498eb0c9d1@kernel.org \
--to=matttbe@kernel.org \
--cc=martineau@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