The 15 patch limit is intended by the maintainers to cover all outstanding patches on the mailing list, not just those in a single patchset. Document this practice accordingly.
Signed-off-by: Simon Horman <[email protected]> --- Documentation/process/maintainer-netdev.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst index 989192421cc9db6c93c816f2dfb7afbe48dd25fc..d98d2f46129eb0eaf55e5106d50b214ddc7bfb67 100644 --- a/Documentation/process/maintainer-netdev.rst +++ b/Documentation/process/maintainer-netdev.rst @@ -363,6 +363,14 @@ just do it. As a result, a sequence of smaller series gets merged quicker and with better review coverage. Re-posting large series also increases the mailing list traffic. +Limit patches outstanding on mailing list +----------------------------------------- + +Avoid having more than 15 patches, across all series, outstanding for +review on the mailing list. This limit is intended to focus developer +effort on testing patches before upstream review. Aiding the quality of +upstream submissions, and easing the load on reviewers. + .. _rcs: Local variable ordering ("reverse xmas tree", "RCS")
