From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>
Subject: [PATCH mptcp-next v2 0/3] doc: introduce MPTCP global doc
Date: Sat, 18 May 2024 17:52:40 +0200 [thread overview]
Message-ID: <20240518-mptcp-doc-v2-0-68304a17cd7d@kernel.org> (raw)
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.
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Changes in v2:
- patch 2/3: make it clearer it is OK to do such modifications for the
backports by adding a note about that in the commit message (Mat).
- patch 3/3: applied Mat's comments.
- Link to v1: https://lore.kernel.org/r/20240517-mptcp-doc-v1-0-fc1ef063584e@kernel.org
---
Matthieu Baerts (NGI0) (3):
doc: mptcp: add missing 'available_schedulers' entry
doc: mptcp: alphabetical order
doc: new 'mptcp' page in 'networking'
Documentation/networking/index.rst | 1 +
Documentation/networking/mptcp-sysctl.rst | 74 +++++++-------
Documentation/networking/mptcp.rst | 156 ++++++++++++++++++++++++++++++
MAINTAINERS | 2 +-
4 files changed, 197 insertions(+), 36 deletions(-)
---
base-commit: 2ccd59d4df6aef3f553caf11e00af66300448e63
change-id: 20240517-mptcp-doc-315f909a12c4
Best regards,
--
Matthieu Baerts (NGI0) <matttbe@kernel.org>
next reply other threads:[~2024-05-18 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 15:52 Matthieu Baerts (NGI0) [this message]
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
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=20240518-mptcp-doc-v2-0-68304a17cd7d@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