From 81583f2a55d25fcba3454f60a979dfd3a8c67f5c Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Tue, 7 May 2024 12:03:10 +0200 Subject: pkg/subsystem: don't Cc some parent subsystems Our fs is more generic than it was defined in MAINTAINERS. Let's not spam its mailing lists with bugs from individual filesystem implementations. --- pkg/subsystem/linux/rules.go | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'pkg/subsystem/linux/rules.go') diff --git a/pkg/subsystem/linux/rules.go b/pkg/subsystem/linux/rules.go index dd46bc1d1..ecc05e5ec 100644 --- a/pkg/subsystem/linux/rules.go +++ b/pkg/subsystem/linux/rules.go @@ -14,6 +14,8 @@ type customRules struct { extraSubsystems map[string][]string // For these subsystems we do not generate monthly reminders. noReminders map[string]struct{} + // We don't want to tag these subsystems in the reports of its sub-subsystem bugs. + noIndirectCc map[string]struct{} // Extra child->[]parent links (on top of the inferred ones). addParents map[string][]string } @@ -105,5 +107,8 @@ var ( // By MAINTAINERS, wireless is somewhat separate, but it's better to keep it as a net child. "wireless": {"net"}, }, + noIndirectCc: map[string]struct{}{ + "fs": {}, + }, } ) -- cgit mrf-deployment