workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2] docs: netdev: refine 15-patch limit
@ 2026-01-15 13:54 Simon Horman
  2026-01-19 14:18 ` patchwork-bot+netdevbpf
  0 siblings, 1 reply; 2+ messages in thread
From: Simon Horman @ 2026-01-15 13:54 UTC (permalink / raw)
  To: David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
	Jonathan Corbet
  Cc: netdev, workflows, linux-doc

The 15 patch limit is intended by the maintainers to cover
all outstanding patches on the mailing list on a per-tree basis.
Not just those in a single patchset. Document this practice accordingly.

Signed-off-by: Simon Horman <horms@kernel.org>
---
Changes in v2:
- Clarify that the limit is per-tree. (Jakub)
- Link to v1: https://lore.kernel.org/r/20260113-15-minutes-of-fame-v1-1-0806b418c6fd@kernel.org
---
 Documentation/process/maintainer-netdev.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst
index 989192421cc9db6c93c816f2dfb7afbe48dd25fc..6bce4507d5d3136270bbf552880451e08b137b61 100644
--- a/Documentation/process/maintainer-netdev.rst
+++ b/Documentation/process/maintainer-netdev.rst
@@ -363,6 +363,18 @@ 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 for a single tree. In other words, a maximum of
+15 patches under review on net, and a maximum of 15 patches under review on
+net-next.
+
+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")




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH v2] docs: netdev: refine 15-patch limit
  2026-01-15 13:54 [PATCH v2] docs: netdev: refine 15-patch limit Simon Horman
@ 2026-01-19 14:18 ` patchwork-bot+netdevbpf
  0 siblings, 0 replies; 2+ messages in thread
From: patchwork-bot+netdevbpf @ 2026-01-19 14:18 UTC (permalink / raw)
  To: Simon Horman
  Cc: davem, edumazet, kuba, pabeni, corbet, netdev, workflows, linux-doc

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 15 Jan 2026 13:54:00 +0000 you wrote:
> The 15 patch limit is intended by the maintainers to cover
> all outstanding patches on the mailing list on a per-tree basis.
> Not just those in a single patchset. Document this practice accordingly.
> 
> Signed-off-by: Simon Horman <horms@kernel.org>
> ---
> Changes in v2:
> - Clarify that the limit is per-tree. (Jakub)
> - Link to v1: https://lore.kernel.org/r/20260113-15-minutes-of-fame-v1-1-0806b418c6fd@kernel.org
> 
> [...]

Here is the summary with links:
  - [v2] docs: netdev: refine 15-patch limit
    https://git.kernel.org/netdev/net/c/ff7737946812

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-01-19 14:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-01-15 13:54 [PATCH v2] docs: netdev: refine 15-patch limit Simon Horman
2026-01-19 14:18 ` patchwork-bot+netdevbpf

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox