From: Jakub Kicinski <kuba@kernel.org>
To: Jingxuan Xie <jingxuanxie@deeproute.ai>
Cc: netdev@vger.kernel.org,
"Willem de Bruijn" <willemdebruijn.kernel@gmail.com>,
韩少阳 <shaoyanghan@deeproute.ai>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Clark Williams" <clrkwllms@kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"John Ogness" <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net v5] af_packet: avoid waiting for TPACKET_V3 copies at retirement
Date: Tue, 17 Nov 2026 17:48:05 -0800 [thread overview]
Message-ID: <20261117174805.709ad32d@kernel.org> (raw)
In-Reply-To: <20261113023809.24730-1-jingxuanxie@deeproute.ai>
On Fri, 13 Nov 2026 02:38:09 +0000 Jingxuan Xie wrote:
> Subject: [PATCH net v5] af_packet: avoid waiting for TPACKET_V3 copies at retirement
Doesn't apply, again. Looks like you are sending these patches twice.
One submission looks normal but there's a submission with the same
Message-ID carrying a weird secrecy / confidentiality clause.
Lore shows both:
https://lore.kernel.org/all/20261113023809.24730-1-jingxuanxie@deeproute.ai/
I'm not touching these patches if they are "considered top-secret
documents". Please submit these without the "secret twin" posting.
--
pw-bot: cr
prev parent reply other threads:[~2026-11-18 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 2:38 Jingxuan Xie
2026-11-13 15:11 ` Willem de Bruijn
2026-11-18 1:48 ` Jakub Kicinski [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=20261117174805.709ad32d@kernel.org \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jingxuanxie@deeproute.ai \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shaoyanghan@deeproute.ai \
--cc=willemdebruijn.kernel@gmail.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
all inboxes | Powered by JetHome®