Date: Wed, 20 Dec 2017 14:00:40 -0500 (EST)
Message-Id: <20171220.140040.1247383563394752781.davem@davemloft.net>
To: laoar.shao@gmail.com
Cc: songliubraving@fb.com, marcelo.leitner@gmail.com, rostedt@goodmis.org,
        bgregg@netflix.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/5] replace tcp_set_state tracepoint with
 inet_sock_set_state
From: David Miller <davem@davemloft.net>
In-Reply-To: <1513739574-3345-1-git-send-email-laoar.shao@gmail.com>
References: <1513739574-3345-1-git-send-email-laoar.shao@gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 859
Lines: 21

From: Yafang Shao <laoar.shao@gmail.com>
Date: Wed, 20 Dec 2017 11:12:49 +0800

> According to the discussion in the mail thread
> https://patchwork.kernel.org/patch/10099243/,
> tcp_set_state tracepoint is renamed to inet_sock_set_state tracepoint and is
> moved to include/trace/events/sock.h.
> 
> With this new tracepoint, we can trace AF_INET/AF_INET6 sock state transitions.
> As there's only one single tracepoint for inet, so I didn't create a new trace
> file named trace/events/inet_sock.h, and just place it in
> include/trace/events/sock.h
> 
> Currently TCP/DCCP/SCTP state transitions are traced with this tracepoint.
> 
> - Why not more protocol ?
> If we really think that anonter protocol should be traced, I will modify the
> code to trace it.
> I just want to make the code easy and not output useless information.

Series applied, thanks.