From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org, netdev@vger.kernel.org,
kernel-team@cloudflare.com
Subject: Re: [PATCH] ip.7: Document IP_LOCAL_PORT_RANGE socket option
Date: Fri, 3 Feb 2023 10:58:52 -0800 [thread overview]
Message-ID: <20230203105852.573a9a35@hermes.local> (raw)
In-Reply-To: <20230201123634.284689-1-jakub@cloudflare.com>
On Wed, 1 Feb 2023 13:36:34 +0100
Jakub Sitnicki <jakub@cloudflare.com> wrote:
> Linux commit 91d0b78c5177 ("inet: Add IP_LOCAL_PORT_RANGE socket option")
> introduced a new socket option available for AF_INET and AF_INET6 sockets.
>
> Option will be available starting from Linux 6.3. Document it.
>
> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
> ---
> Submitting this man page update as the author of the feature.
>
> We did a technical review of the man page text together with the code [1].
>
> [1]: https://lore.kernel.org/all/20221221-sockopt-port-range-v6-0-be255cc0e51f@cloudflare.com/
> ---
> man7/ip.7 | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
Marking this patch as not applicable in netdev patchwork since it is for documentation
and I assume linux-man has its own tracking.
next prev parent reply other threads:[~2023-02-03 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 12:36 [PATCH] ip.7: Document IP_LOCAL_PORT_RANGE socket option Jakub Sitnicki
2023-02-03 18:58 ` Stephen Hemminger [this message]
2023-02-03 19:09 ` Simon Horman
2023-02-05 13:16 ` Alejandro Colomar
2023-02-06 10:42 ` Jakub Sitnicki
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=20230203105852.573a9a35@hermes.local \
--to=stephen@networkplumber.org \
--cc=alx.manpages@gmail.com \
--cc=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
/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