From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yafang Shao <laoar.shao@gmail.com>,
davem@davemloft.net, edumazet@google.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: clean up STATE_TRACE
Date: Wed, 14 Nov 2018 07:44:25 -0800 [thread overview]
Message-ID: <74f5b61e-eb66-4c34-dfb7-1f746761939a@gmail.com> (raw)
In-Reply-To: <1542205577-21925-1-git-send-email-laoar.shao@gmail.com>
On 11/14/2018 06:26 AM, Yafang Shao wrote:
> Currently we can use bpf or tcp tracepoint to conveniently trace the tcp
> state transition at the run time.
> So we don't need to do this stuff at the compile time anymore.
>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> ---
> include/net/tcp.h | 12 ------------
> net/ipv4/tcp.c | 4 ----
> 2 files changed, 16 deletions(-)
Yes, sure.
Signed-off-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2018-11-14 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 14:26 [PATCH net-next] tcp: clean up STATE_TRACE Yafang Shao
2018-11-14 15:44 ` Eric Dumazet [this message]
2018-11-17 4:28 ` David Miller
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=74f5b61e-eb66-4c34-dfb7-1f746761939a@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).