linux-kernel - Re: [PATCH] docs: submitting-patches: encourage direct notifications to reviewers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZRpkWXMiQjUJPszZ@infradead.org>
Date:   Sun, 1 Oct 2023 23:34:01 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Thomas Weißschuh <linux@...ssschuh.net>
Cc:     Christoph Hellwig <hch@...radead.org>,
        Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: encourage direct notifications
 to reviewers

On Fri, Sep 29, 2023 at 09:24:57AM +0200, Thomas Weißschuh wrote:
> > This does not scale.
> 
> Could you elaborate in which way it doesn't scale?

If I send a modest cross-subsystem series it often touches 20+
subsystems.  Between mailing lists and maintainers that's usually
already 60+ recipients.  If you now add a another 2-3 maintainers
we're just going to hit limits in mail servers.

> > Please read the mailinglist, that's the whole
> > point of having it.
> 
> When reviewing things in various subsystem this would require reading
> all of LKML, which is impractical.

Works with your maintainers to have useful lists for their subsystems.
That's again the point.