From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH v5 net-next] net/tcp: trace all TCP/IP state transition
 with tcp_set_state tracepoint
Date: Fri, 08 Dec 2017 11:03:59 -0500 (EST)
Message-ID: <20171208.110359.272239843105611340.davem@davemloft.net>
References: <CALOAHbAixEmBFTuTD42GtC6sbqdguGVSEX8w6+GTw6rLRwRuUQ@mail.gmail.com>
        <CALOAHbBbo+ueVt7Wu=wAvgrfFjg7LVHfo4W_hhv_d7pQzeY9+Q@mail.gmail.com>
        <20171208110356.GS13341@localhost.localdomain>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: laoar.shao@gmail.com, songliubraving@fb.com, kuznet@ms2.inr.ac.ru,
        yoshfuji@linux-ipv6.org, rostedt@goodmis.org, bgregg@netflix.com,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
To: marcelo.leitner@gmail.com
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20171208110356.GS13341@localhost.localdomain>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Date: Fri, 8 Dec 2017 09:03:56 -0200

> I'm okay with this v5 then, can't see a better way around it.

I would suggest not making this a TCP specific feature.

Because socket state changes are not a TCP specific behavior.