Re: [PATCH net-next] docs: exclude driver and netdevsim bugs

[Leon Romanovsky <leon@kernel.org>]

On Wed, Jun 03, 2026 at 09:29:43AM -0700, Jakub Kicinski wrote:
> Initial wave of AI-generated fixes was mostly for core and protocols
> we care about. But the number of irrelevant driver fixes is slowly
> increasing. Add a section of explicit exclusions to our maintainer
> profile.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: corbet@lwn.net
> CC: skhan@linuxfoundation.org
> CC: workflows@vger.kernel.org
> CC: linux-doc@vger.kernel.org
> ---
>  Documentation/process/maintainer-netdev.rst | 28 +++++++++++++++++++++
>  1 file changed, 28 insertions(+)
> 
> diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst
> index ec7b9aa2877f..cc4b5fa3b5c1 100644
> --- a/Documentation/process/maintainer-netdev.rst
> +++ b/Documentation/process/maintainer-netdev.rst
> @@ -272,6 +272,34 @@ the case today. Please follow the standard stable rules in
>  :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`,
>  and make sure you include appropriate Fixes tags!
>  
> +Bug fixes
> +~~~~~~~~~
> +
> +Unless explicitly excluded all bug fixes should be targeting the ``net``
> +tree and contain an appropriate Fixes tag.
> +
> +Obvious exclusions:
> +
> + - fixes for bugs which only exist in ``net-next`` should target ``net-next``
> +   (please still include the Fixes tag in the commit message)
> + - bugs which cannot be reached, e.g. in code paths not executed given
> +   current in-tree callers
> + - fixes for compiler warnings and typos

If you decide to resubmit this patch, could you please remove "fixes for
compiler warnings" from the exclusion list?

It is quite frustrating to receive a compiler warning originating from a
different subsystem after the merge window, knowing it will not be
addressed until the next merge window (around eight weeks later).

Thanks.