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, matttbe@kernel.org,
martineau@kernel.org, geliang@kernel.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next 0/6] Implement reset reason mechanism to detect
Date: Wed, 3 Apr 2024 18:50:33 -0700 [thread overview]
Message-ID: <20240403185033.47ebc6a9@kernel.org> (raw)
In-Reply-To: <20240403073144.35036-1-kerneljasonxing@gmail.com>
On Wed, 3 Apr 2024 15:31:38 +0800 Jason Xing wrote:
> It's based on top of https://patchwork.kernel.org/project/netdevbpf/list/?series=840182
Please post as RFC if there's a dependency.
We don't maintain patch queues for people.
--
pw-bot: cr
next prev parent reply other threads:[~2024-04-04 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 7:31 [PATCH net-next 0/6] Implement reset reason mechanism to detect Jason Xing
2024-04-03 7:31 ` [PATCH net-next 1/6] net: introduce rstreason to detect why the RST is sent Jason Xing
2024-04-03 7:31 ` [PATCH net-next 2/6] rstreason: prepare for passive reset Jason Xing
2024-04-03 7:31 ` [PATCH net-next 3/6] rstreason: prepare for active reset Jason Xing
2024-04-03 7:31 ` [PATCH net-next 4/6] tcp: support rstreason for passive reset Jason Xing
2024-04-03 7:31 ` [PATCH net-next 5/6] mptcp: " Jason Xing
2024-04-03 7:31 ` [PATCH net-next 6/6] rstreason: make it work in trace world Jason Xing
2024-04-04 1:50 ` Jakub Kicinski [this message]
2024-04-04 1:57 ` [PATCH net-next 0/6] Implement reset reason mechanism to detect Jason Xing
-- strict thread matches above, loose matches on Subject: below --
2024-04-04 7:20 Jason Xing
2024-04-04 8:16 ` MPTCP CI
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=20240403185033.47ebc6a9@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=matttbe@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mptcp@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.