Re: [PATCH 2/2] docs: submitting-patches: mention the branch in T: entries

[Krzysztof Kozlowski <krzk@kernel.org>]

On 24/09/2026 05:35, Matthias Goergens wrote:
> A git T: entry in MAINTAINERS may name a branch after the repository
> URL, and where it does, that branch rather than the repository's HEAD
> is the one to prepare patches against.  Say so where contributors are
> sent to the T: entry.
> 
> Suggested-by: Theodore Ts'o <tytso@mit.edu>
> Link: https://lore.kernel.org/all/arSMwd1bGO1vrif-@mit.edu/
> Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
> ---
>  Documentation/process/submitting-patches.rst | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index 7ae79452e1b4..2936388dcaee 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -37,8 +37,9 @@ which can be grabbed with::
>  Note, however, that you may not want to develop against the mainline tree
>  directly.  Most subsystem maintainers run their own trees and want to see
>  patches prepared against those trees.  See the **T:** entry for the subsystem
> -in the MAINTAINERS file to find that tree, or simply ask the maintainer if
> -the tree is not listed there.
> +in the MAINTAINERS file to find that tree, and the branch to work against if
> +the entry names one, or simply ask the maintainer if the tree is not listed
> +there.

Honestly this should be squashed with previous. It is one logical change
- amend format of T: entry and update the docs which reference that T:.

Best regards,
Krzysztof