From: Jakub Kicinski <kuba@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Simon Horman <horms@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>
Subject: Re: [PATCH] net/tcp_ao: tracing: Hide tcp_ao events under CONFIG_TCP_AO
Date: Mon, 16 Jun 2025 13:18:25 -0700 [thread overview]
Message-ID: <20250616131825.65e1c058@kernel.org> (raw)
In-Reply-To: <20250616144718.4e8e12bf@batman.local.home>
On Mon, 16 Jun 2025 14:47:18 -0400 Steven Rostedt wrote:
> On Sat, 14 Jun 2025 16:30:03 +0100
> Simon Horman <horms@kernel.org> wrote:
>
> > I agree that the events and classes covered by this #define
> > are not used unless CONFIG_TCP_AO is set. And that the small
> > number of TCP_AO related events that are left outside
> > the define are used even when CONFIG_TCP_AO is not set.
> >
> > Reviewed-by: Simon Horman <horms@kernel.org>
>
> Should I take this or should this go through the networking tree?
Weak preference towards networking tree. We'll apply by the end of
the day.
next prev parent reply other threads:[~2025-06-16 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 13:46 [PATCH] net/tcp_ao: tracing: Hide tcp_ao events under CONFIG_TCP_AO Steven Rostedt
2025-06-14 15:30 ` Simon Horman
2025-06-16 18:47 ` Steven Rostedt
2025-06-16 20:18 ` Jakub Kicinski [this message]
2025-06-16 20:20 ` Steven Rostedt
2025-06-16 22:10 ` patchwork-bot+netdevbpf
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=20250616131825.65e1c058@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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).