From: Jakub Kicinski <kuba@kernel.org>
To: Zheao Li <me@manjusaka.me>
Cc: edumazet@google.com, mhiramat@kernel.org, rostedt@goodmis.org,
davem@davemloft.net, dsahern@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: Mon, 28 Aug 2023 12:45:57 -0700 [thread overview]
Message-ID: <20230828124557.0cc70e58@kernel.org> (raw)
In-Reply-To: <20230825133246.344364-1-me@manjusaka.me>
On Fri, 25 Aug 2023 13:32:47 +0000 Zheao Li wrote:
> This the 4th version of the patch, the previous discusstion is here
>
> https://lore.kernel.org/linux-trace-kernel/20230807183308.9015-1-me@manjusaka.me/
>
> In this version of the code, here's some different:
>
> 1. The event name has been changed from `tcp_ca_event_set` to
> `tcp_ca_event`
>
> 2. Output the current protocol family in TP_printk
>
> 3. Show the ca_event symbol instead of the original number
>
> But the `./scripts/checkpatch.pl` has been failed to check this patch,
> because we sill have some code error in ./scripts/checkpatch.pl(in
> another world, the test would be failed when we use the
> scripts/checkpatch.pl to check the events/tcp.h
>
> Feel free to ask me if you have have any issues and ideas.
## Form letter - net-next-closed
The merge window for v6.6 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations.
We are currently accepting bug fixes only.
Please repost when net-next reopens after Sept 11th.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
next prev parent reply other threads:[~2023-08-28 19:46 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 [this message]
2023-09-17 14:06 ` Manjusaka
2023-09-17 15:12 ` Steven Rostedt
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=20230828124557.0cc70e58@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--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 \
--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