> On Nov 26, 2025, at 6:16 AM, Paolo Abeni <[email protected]> wrote: > > On 11/25/25 9:00 PM, Jon Kohler wrote: >>> On Nov 25, 2025, at 12:57 PM, Paolo Abeni <[email protected]> wrote: >>> >>> CC netdev >> >> Thats odd, I used git send-email --to-cmd='./scripts/get_maintainer.pl, >> but it looks like in MAINTAINERS, that only would have hit >> VIRTIO CORE AND NET DRIVERS, > > ?!? not here: > > ./scripts/get_maintainer.pl drivers/net/virtio_net.c > "Michael S. Tsirkin" <[email protected]> (maintainer:VIRTIO CORE AND NET > DRIVERS) > Jason Wang <[email protected]> (maintainer:VIRTIO CORE AND NET DRIVERS) > Xuan Zhuo <[email protected]> (reviewer:VIRTIO CORE AND NET > DRIVERS) > "Eugenio Pérez" <[email protected]> (reviewer:VIRTIO CORE AND NET DRIVERS) > Andrew Lunn <[email protected]> (maintainer:NETWORKING DRIVERS) > "David S. Miller" <[email protected]> (maintainer:NETWORKING DRIVERS) > Eric Dumazet <[email protected]> (maintainer:NETWORKING DRIVERS) > Jakub Kicinski <[email protected]> (maintainer:NETWORKING DRIVERS) > Paolo Abeni <[email protected]> (maintainer:NETWORKING DRIVERS) > [email protected] (open list:VIRTIO CORE AND NET DRIVERS) > [email protected] (open list:NETWORKING DRIVERS) > [email protected] (open list) > > The "NETWORKING DRIVER" entry should catch even virtio_net. Something > odd in your setup?!?
Literally all I’ve got is a clone of net-next and using get_maintainer.pl but yea the issue is the header-only change. I have a knack for falling exactly into these sorts of process holes :) It’ll be a good cleanup anyhow > > BTW, this is a bit too late, but you should wait at least 24h before > reposting on netdev: Thanks for the guidance again, I’ll be sure to pace things out if/when I find myself in this situation again! I appreciate the help
