From: Qi Tang <tpluszz77@gmail.com>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com
Cc: netdev@vger.kernel.org, lyutoon@gmail.com, dsahern@kernel.org,
idosch@nvidia.com, horms@kernel.org, paul@paul-moore.com,
huw@codeweavers.com, linux-security-module@vger.kernel.org,
Qi Tang <tpluszz77@gmail.com>
Subject: Re: [PATCH net 0/4] net: trust-after-modification fixes for IPv4 options + netlabel
Date: Fri, 15 May 2026 01:06:13 +0800 [thread overview]
Message-ID: <20260514170613.4098569-1-tpluszz77@gmail.com> (raw)
In-Reply-To: <20260514165139.436961-1-tpluszz77@gmail.com>
Sorry, v1 went out unthreaded and 1/4 was duplicated. I will
resend properly as [PATCH net v2 0/4] in ~24h. Please ignore
the v1 thread.
Qi Tang <tpluszz77@gmail.com>
Tong Liu <lyutoon@gmail.com>
prev parent reply other threads:[~2026-05-14 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 16:51 [PATCH net 0/4] net: trust-after-modification fixes for IPv4 options + netlabel Qi Tang
2026-05-14 17:06 ` Qi Tang [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=20260514170613.4098569-1-tpluszz77@gmail.com \
--to=tpluszz77@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=huw@codeweavers.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lyutoon@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.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