From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev-bot+sinfo@kernel.org,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
Chris Mason <mason@kernel.org>, Kyle Zeng <kylebot@openai.com>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net] net: skbuff: uncharge trimmed zerocopy frags on error
Date: Thu, 05 Nov 2026 17:39:14 -0500 [thread overview]
Message-ID: <willemdebruijn.kernel.1d573ca061134@gmail.com> (raw)
In-Reply-To: <179391822817.488859.907054151678387708@kernel.org>
netdev-bot+sinfo@ 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.
I thought "The issue was found by an LLM." in the commit message would be
sufficient.
This was found through analysis. A repro can be built, but its output
only pollutes the commit message imho.
> 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.
next prev parent reply other threads:[~2026-11-05 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 22:35 [PATCH net] net: skbuff: uncharge trimmed zerocopy frags on error Willem de Bruijn
2026-11-05 22:37 ` netdev-bot+sinfo
2026-11-05 22:39 ` Willem de Bruijn [this message]
2026-11-10 23:22 ` Jakub Kicinski
2026-11-10 23: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=willemdebruijn.kernel.1d573ca061134@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kylebot@openai.com \
--cc=mason@kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 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.