From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>,
mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Gregory Detal <gregory.detal@gmail.com>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] doc: mptcp: new general doc and fixes
Date: Wed, 22 May 2024 11:45:07 +0200 [thread overview]
Message-ID: <33c849d2-994b-4380-a177-88412e698615@kernel.org> (raw)
In-Reply-To: <8945a5ae3f94572daae42d4bfdc326bcf0889964.camel@redhat.com>
Hi Paolo,
On 22/05/2024 11:35, Paolo Abeni wrote:
> Hi,
>
> On Mon, 2024-05-20 at 10:16 +0200, Matthieu Baerts (NGI0) wrote:
>> A general documentation about MPTCP was missing since its introduction
>> in v5.6. The last patch adds a new 'mptcp' page in the 'networking'
>> documentation.
>>
>> The first patch is a fix for a missing sysctl entry introduced in v6.10
>> rc0, and the second one reorder the sysctl entries.
>>
>> These patches can be applied without conflicts on top of the 'net' tree
>> and the 'docs-next' one. They are currently based on top of the current
>> 'net' tree because the first patch is a fix for a patch that is not in
>> 'docs-next' yet.
>>
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
> These patches are IMHO net-next material. If you don't mind I'll defer
> them.
No problem, my bad, I thought it was OK to send new doc about existing
features and missing items to -net. I will re-send them next week,
targetting net-next then.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-05-22 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 8:16 [PATCH net 0/3] doc: mptcp: new general doc and fixes Matthieu Baerts (NGI0)
2024-05-20 8:16 ` [PATCH net 1/3] doc: mptcp: add missing 'available_schedulers' entry Matthieu Baerts (NGI0)
2024-05-20 8:16 ` [PATCH net 2/3] doc: mptcp: alphabetical order Matthieu Baerts (NGI0)
2024-05-20 8:16 ` [PATCH net 3/3] doc: new 'mptcp' page in 'networking' Matthieu Baerts (NGI0)
2024-05-22 9:35 ` [PATCH net 0/3] doc: mptcp: new general doc and fixes Paolo Abeni
2024-05-22 9:45 ` 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=33c849d2-994b-4380-a177-88412e698615@kernel.org \
--to=matttbe@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=gregory.detal@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.