From: Fernando Fernandez Mancera <fmancera@suse.de>
To: netdev-bot+sinfo@kernel.org
Cc: netdev@vger.kernel.org, dev@openvswitch.org, blp@nicira.com,
joe@wand.net.nz, jesse@nicira.com, horms@kernel.org,
pabeni@redhat.com, kuba@kernel.org, edumazet@kernel.org,
davem@davemloft.net, i.maximets@ovn.org, echaudro@redhat.com,
aconole@redhat.com
Subject: Re: [PATCH net-next v2] net: openvswitch: do not set transport header on later IPv4 fragments
Date: Mon, 5 Oct 2026 17:14:34 +0200 [thread overview]
Message-ID: <893302a7-ce9c-4765-8788-08f7eb4b1f37@suse.de> (raw)
In-Reply-To: <179121321982.1402591.7112090306604732381@kernel.org>
On 10/5/26 5:13 PM, netdev-bot+sinfo@kernel.org wrote:
> Hi!
>
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
>
> - Whether the issue was actually triggered, or is only theoretical
> (e.g. found by code inspection). If it was triggered please include
> the symptoms, like the stack trace or error messages.
>
> Please do not repost the series just to address the above. Instead,
> reply to this email with the missing information, so that reviewers
> can take it into account. If the series needs another revision for
> other reasons, please include the information in the commit messages
> then.
>
> The evaluation is done by an LLM so it may be wrong, if you think
> that is the case please reply and explain.
It is a fix that was spotted by sashiko as noted on the patch note under
the commit message. Anyway, I believe this should go to net-next, no
user ever spotted this issue.
next prev parent reply other threads:[~2026-10-05 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:08 [PATCH net-next v2] net: openvswitch: do not set transport header on later IPv4 fragments Fernando Fernandez Mancera
2026-10-05 15:13 ` netdev-bot+sinfo
2026-10-05 15:14 ` Fernando Fernandez Mancera [this message]
2026-10-08 3:08 ` netdev-bot+sashiko
2026-10-08 12:24 ` Fernando Fernandez Mancera
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=893302a7-ce9c-4765-8788-08f7eb4b1f37@suse.de \
--to=fmancera@suse.de \
--cc=aconole@redhat.com \
--cc=blp@nicira.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=jesse@nicira.com \
--cc=joe@wand.net.nz \
--cc=kuba@kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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