From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Wei Wang <weiwan@google.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org
Cc: netdev@vger.kernel.org, Yuchung Cheng <ycheng@google.com>,
Neal Cardwell <ncardwell@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [patch v3] tcp.7: Add description for TCP_FASTOPEN and TCP_FASTOPEN_CONNECT options
Date: Sat, 16 Oct 2021 00:12:08 +0200 [thread overview]
Message-ID: <6c5ac9d3-9e9a-12aa-7dc8-d89553790e7b@gmail.com> (raw)
In-Reply-To: <CAEA6p_CSbFFiEUQKy_n5dBd-oBWLq1L0CZYjECqBfjjkeQoSdg@mail.gmail.com>
Hi Wei,
On 10/15/21 6:08 PM, Wei Wang wrote:
> On Fri, Sep 24, 2021 at 4:54 PM Wei Wang <weiwan@google.com> wrote:
>>
>> TCP_FASTOPEN socket option was added by:
>> commit 8336886f786fdacbc19b719c1f7ea91eb70706d4
>> TCP_FASTOPEN_CONNECT socket option was added by the following patch
>> series:
>> commit 065263f40f0972d5f1cd294bb0242bd5aa5f06b2
>> commit 25776aa943401662617437841b3d3ea4693ee98a
>> commit 19f6d3f3c8422d65b5e3d2162e30ef07c6e21ea2
>> commit 3979ad7e82dfe3fb94a51c3915e64ec64afa45c3
>> Add detailed description for these 2 options.
>> Also add descriptions for /proc entry tcp_fastopen and tcp_fastopen_key.
>>
>> Signed-off-by: Wei Wang <weiwan@google.com>
>> ---
>
> Hi Alex,
>
> Does this version look OK to you to apply?
> Let me know.
Sorry, I missed that patch.
Thanks for the ping! I'll try to have a look at it ASAP.
Thanks,
Alex
>
> Thanks.
> Wei
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-10-15 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 23:54 [patch v3] tcp.7: Add description for TCP_FASTOPEN and TCP_FASTOPEN_CONNECT options Wei Wang
2021-10-15 16:08 ` Wei Wang
2021-10-15 22:12 ` Alejandro Colomar (man-pages) [this message]
2021-11-05 17:19 ` Wei Wang
2021-11-12 20:55 ` Alejandro Colomar (man-pages)
2021-11-12 20:58 ` Wei Wang
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=6c5ac9d3-9e9a-12aa-7dc8-d89553790e7b@gmail.com \
--to=alx.manpages@gmail.com \
--cc=edumazet@google.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=weiwan@google.com \
--cc=ycheng@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox