linux-kernel - Re: [PATCH v2] Documentation/process: always CC responsible lists

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: <877cu6ttvj.fsf@meer.lwn.net>
Date:   Thu, 20 Apr 2023 10:12:48 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     Markus Schneider-Pargmann <msp@...libre.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v2] Documentation/process: always CC responsible lists

Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> writes:

> The "Select the recipients for your patch" part about CC-ing mailing
> lists is a bit vague and might be understood that only some lists should
> be Cc-ed.  That's not what most of the maintainers expect.  For given
> code, associated mailing list must always be CC-ed, because the list is
> used for reviewing and testing patches.  Example are the Devicetree
> bindings patches, which are tested iff Devicetree mailing list is CC-ed.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>
Applied, thanks.

jon