From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: edumazet@google.com, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, rostedt@goodmis.org,
pabeni@redhat.com, davem@davemloft.net, netdev@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next v2 0/3] tcp: make trace of reset logic complete
Date: Mon, 25 Mar 2024 18:30:33 -0700 [thread overview]
Message-ID: <20240325183033.79107f1d@kernel.org> (raw)
In-Reply-To: <20240325062831.48675-1-kerneljasonxing@gmail.com>
On Mon, 25 Mar 2024 14:28:28 +0800 Jason Xing wrote:
> Before this, we miss some cases where the TCP layer could send rst but
> we cannot trace it. So I decided to complete it :)
>
> v2
> 1. fix spelling mistakes
Not only do you post it before we "officially" open net-next but
also ignoring the 24h wait period.
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#tl-dr
The main goal of the 24h rule is to stop people from bombarding us with
new versions for silly reasons.
You show know better than this, it's hardly your first contribution :(
--
pv-bot: 24h
next prev parent reply other threads:[~2024-03-26 1:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 6:28 [PATCH net-next v2 0/3] tcp: make trace of reset logic complete Jason Xing
2024-03-25 6:28 ` [PATCH net-next v2 1/3] trace: adjust TP_STORE_ADDR_PORTS_SKB() parameters Jason Xing
2024-03-25 6:28 ` [PATCH net-next v2 2/3] trace: tcp: fully support trace_tcp_send_reset Jason Xing
2024-03-25 6:28 ` [PATCH net-next v2 3/3] tcp: add location into reset trace process Jason Xing
2024-03-26 11:08 ` Paolo Abeni
2024-03-29 1:15 ` Jakub Kicinski
2024-03-29 2:53 ` Jason Xing
2024-03-26 1:30 ` Jakub Kicinski [this message]
2024-03-26 2:13 ` [PATCH net-next v2 0/3] tcp: make trace of reset logic complete Jason Xing
2024-03-26 2:23 ` Jakub Kicinski
2024-03-26 2:33 ` Jason Xing
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=20240325183033.79107f1d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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;
as well as URLs for NNTP newsgroup(s).