On Mon, Aug 03, 2020 at 06:32:24PM +0100, Russell King - ARM Linux admin wrote: > On Mon, Aug 03, 2020 at 10:21:04AM -0700, Eric Biggers wrote: > > On Mon, Aug 03, 2020 at 06:12:33PM +0100, Russell King - ARM Linux admin wrote: > > > Dear syzbot, > > > > > > Please explain why you are spamming me with all these reports - four so > > > far. I don't understand why you think I should be doing anything with > > > these. > > > > > > Thanks. > > > > syzbot just uses get_maintainer.pl. > > > > $ ./scripts/get_maintainer.pl net/bluetooth/hci_event.c > > Marcel Holtmann <marcel@xxxxxxxxxxxx> (maintainer:BLUETOOTH SUBSYSTEM) > > Johan Hedberg <johan.hedberg@xxxxxxxxx> (maintainer:BLUETOOTH SUBSYSTEM) > > "David S. Miller" <davem@xxxxxxxxxxxxx> (maintainer:NETWORKING [GENERAL]) > > Jakub Kicinski <kuba@xxxxxxxxxx> (maintainer:NETWORKING [GENERAL]) > > Russell King <linux@xxxxxxxxxxxxxxx> (maintainer:SFF/SFP/SFP+ MODULE SUPPORT) > > linux-bluetooth@xxxxxxxxxxxxxxx (open list:BLUETOOTH SUBSYSTEM) > > netdev@xxxxxxxxxxxxxxx (open list:NETWORKING [GENERAL]) > > linux-kernel@xxxxxxxxxxxxxxx (open list) > > Ah, and, because the file mentions "phylink" (although it makes no use > of the phylink code), get_maintainer spits out my address. Great. > > So how do I get get_maintainer to identify patches that are making use > of phylink, but avoid this bluetooth code... (that's not a question.) > I think "K: " (content regex) in MAINTAINERS is best avoided. This isn't the first time that someone has volunteered to maintain all files containing $foo, then complained when they receive emails for those files as they requested... If you do really want to use it, can you use a more specific regex? E.g. a regex that matches "#include <linux/phylink.h>" or some specific function(s)? - Eric
