From: Steven Rostedt <rostedt@goodmis.org>
To: Manjusaka <me@manjusaka.me>
Cc: edumazet@google.com, mhiramat@kernel.org, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v4] tracepoint: add new `tcp:tcp_ca_event` trace event
Date: Sun, 17 Sep 2023 11:12:46 -0400 [thread overview]
Message-ID: <20230917111246.42ecffce@rorschach.local.home> (raw)
In-Reply-To: <c978c5a5-a9a6-41bf-86f2-2eebf6888e1e@manjusaka.me>
On Sun, 17 Sep 2023 22:06:45 +0800
Manjusaka <me@manjusaka.me> wrote:
> Ping to review(
The ask was to resend the patches after the merge window.
-- Steve
prev parent reply other threads:[~2023-09-17 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 13:32 [PATCH v4] tracepoint: add new `tcp:tcp_ca_event` trace event Zheao Li
2023-08-28 19:45 ` Jakub Kicinski
2023-09-17 14:06 ` Manjusaka
2023-09-17 15:12 ` Steven Rostedt [this message]
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=20230917111246.42ecffce@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=me@manjusaka.me \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).