From: Jakub Kicinski <kuba@kernel.org>
To: Nate Karstens <nate.karstens@garmin.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <horms@kernel.org>,
<jacob.e.keller@intel.com>, <john.fastabend@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux@treblig.org>,
<mrpre@163.com>, <nate.karstens@gmail.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<sd@queasysnail.net>, <stable@vger.kernel.org>,
<tom@quantonium.net>
Subject: Re: [PATCH net v2] strparser: Fix signed/unsigned mismatch bug
Date: Thu, 6 Nov 2025 14:22:04 -0800 [thread overview]
Message-ID: <20251106142204.2e5f2227@kernel.org> (raw)
In-Reply-To: <20251106165117.1774787-1-nate.karstens@garmin.com>
On Thu, 6 Nov 2025 10:51:17 -0600 Nate Karstens wrote:
> CONFIDENTIALITY NOTICE: This email and any attachments are for the
> sole use of the intended recipient(s) and contain information that
> may be Garmin confidential and/or Garmin legally privileged. If you
> have received this email in error, please notify the sender by reply
> email and delete the message. Any disclosure, copying, distribution
> or use of this communication (including attachments) by someone other
> than the intended recipient is prohibited. Thank you.
This notice prevents us from doing anything with the patch.
Also please do _not_ send the patches in reply to existing threads.
next prev parent reply other threads:[~2025-11-06 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 17:42 [PATCH] strparser: Fix signed/unsigned mismatch bug Nate Karstens
2025-11-04 23:28 ` Sabrina Dubroca
2025-11-05 17:34 ` Nate Karstens
2025-11-05 22:29 ` Jacob Keller
2025-11-05 23:12 ` Nate Karstens
2025-11-05 23:47 ` Jacob Keller
2025-11-06 15:22 ` Sabrina Dubroca
2025-11-06 16:36 ` Nate Karstens
2025-11-06 16:51 ` [PATCH net v2] " Nate Karstens
2025-11-06 22:22 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 22:28 Nate Karstens
2025-11-07 9:56 ` Jacob Keller
2025-11-07 15:01 ` Sabrina Dubroca
2025-11-08 2:30 ` patchwork-bot+netdevbpf
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=20251106142204.2e5f2227@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mrpre@163.com \
--cc=nate.karstens@garmin.com \
--cc=nate.karstens@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
--cc=tom@quantonium.net \
/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).