netdev - Re: [PATCH net 1/3] docs: netdev: document that patch series length limit

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] [day] [month] [year] [list]

Message-ID: <20220701091638.631b60b0@kernel.org>
Date:   Fri, 1 Jul 2022 09:16:38 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
        pabeni@...hat.com, corbet@....net, linux-doc@...r.kernel.org
Subject: Re: [PATCH net 1/3] docs: netdev: document that patch series length
 limit

On Fri, 1 Jul 2022 09:48:30 +0200 Andrew Lunn wrote:
> > +Put yourself in the shoes of the reviewer. Each patch is read separately
> > +and therefore should constitute a comprehensible step towards your stated
> > +goal. Avoid sending series longer than 15 patches, they clog review queue
> > +and increase mailing list traffic when re-posted.
>
> I think a key concept is, big patch series takes longer to review, so
> needs a bigger junk of time allocated to it, so often gets differed
> until late. As a result, it will take longer to merge. A small series
> can be reviewed in a short time, so Maintainers just do it, allowing
> for quicker merging.

Good point, let me fold that in.