On 10/5/26 6:27 PM, Jakub Kicinski wrote:
On Fri, 2 Oct 2026 09:16:15 -0700 Justin Chen wrote:
quoted
On 10/1/2026 6:41 PM, Jakub Kicinski wrote:
quoted
On Wed, 30 Sep 2026 23:08:43 +0000 netdev-bot+sinfo@kernel.org wrote:
quoted
Hi!
This is an automated message. This series looks like a fix, but its
commit messages seem to be missing some information:
- How the issue was discovered, e.g. hit in production, hit during
development, syzbot report, manual code inspection, LLM or static
analysis tool scan.
- 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.
- What hardware the change was tested on. For driver fixes please
mention the device (and if relevant firmware version) used for
testing, or say that the change was not tested on real hardware.
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.
please respond to this
The issue was hit in production and I verified the sequence keeps the TX
disabled in my standalone test. I tested on an internal development
board with bcm77122, but should be reproducible on any genet HW that
supports power management.
I obviously meant that you should respond to all the fix info requests.
Not just this one in particular.
Sorry Jakub, I am not understanding what you are asking for. I believe I answered the questions above? Or am I missing something else?
Thanks,
Justin