diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-09-30 09:31:09 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-01 18:16:30 -0700 |
| commit | fe8a42931853be7e78564fa6359f4c0197429d1e (patch) | |
| tree | e1aea8fa3bd694034dd7c0a28e48adb6ec564f61 /tools/lib/python/kdoc | |
| parent | 7efc07ad22c390289ec16dc676ac290a3827fac6 (diff) | |
docs: netdev: additional info requirements for bug fixes
Knowing how AI-generated patches were tested would be a great help
when reviewing them. Explicitly ask people to describe the discovery
and validation process they followed.
I posted this as an RFC a while back and there were some concerns
from developers that it would gum up the process. With Linus's
recent complaints about the size of our PRs, we really need
this information. I launched an AI bot which complains if
people don't explain how bugs were discovered and tested
(look for netdev-bot+sinfo@kernel.org, s=series info).
We need to document this requirement.
Reviewed-by: Nicolai Buchwitz <nb@tipi-net.de>
Acked-by: Daniel Machon <daniel.machon@microchip.com>
Link: https://patch.msgid.link/20260930163109.3910509-1-kuba@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc')
0 files changed, 0 insertions, 0 deletions