From: Martin KaFai Lau <martin.lau@linux.dev>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: edumazet@google.com, lixiaoyan@google.com, dsahern@kernel.org,
kuba@kernel.org, weiwan@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Menglong Dong <dongml2@chinatelecom.cn>
Subject: Re: [PATCH bpf-next] net: tcp: replace the document for "lsndtime" in tcp_sock
Date: Tue, 29 Oct 2024 11:42:26 -0700 [thread overview]
Message-ID: <c6a30471-46f2-4cf9-b94c-c0a9119a77ff@linux.dev> (raw)
In-Reply-To: <20241026065422.2820134-1-dongml2@chinatelecom.cn>
On 10/25/24 11:54 PM, Menglong Dong wrote:
> The document for "lsndtime" in struct tcp_sock is placed in the wrong
> place, so let's replace it in the proper place.
The patch lgtm but this should be tagged for net-next material.
next prev parent reply other threads:[~2024-10-29 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 6:54 [PATCH bpf-next] net: tcp: replace the document for "lsndtime" in tcp_sock Menglong Dong
2024-10-29 18:42 ` Martin KaFai Lau [this message]
2024-10-30 1:18 ` Menglong Dong
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=c6a30471-46f2-4cf9-b94c-c0a9119a77ff@linux.dev \
--to=martin.lau@linux.dev \
--cc=dongml2@chinatelecom.cn \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=weiwan@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