From: Damien Le Moal <dlemoal@kernel.org>
To: Matthias Goergens <matthias.goergens@gmail.com>,
Niklas Cassel <cassel@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the libata/linux for-next branch
Date: Thu, 24 Sep 2026 12:52:59 +0900 [thread overview]
Message-ID: <88fb216a-6024-49d2-97ae-79a1592541ff@kernel.org> (raw)
In-Reply-To: <20260924033545.3624716-1-matthias.goergens@gmail.com>
On 9/24/26 12:35, Matthias Goergens wrote:
> The T: entry for LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)
> names libata/linux without a branch. The repository's HEAD (master,
> 8d3ae59288f1) is a commit from 2026-08-16 that mainline already
> contains. linux-next pulls for-next from this repository (Next/Trees,
> next-20260923), and on 2026-09-24 that branch carried work not yet in
> mainline. Name the branch so the entry identifies where development
> happens.
>
> Documentation/process/submitting-patches.rst sends contributors to the
> T: entry to find the tree to prepare patches against, so a branch-less
> entry whose HEAD is already in mainline points them at the wrong tree.
>
> Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
Looks good.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-09-24 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 3:35 [PATCH] MAINTAINERS: name the libata/linux for-next branch Matthias Goergens
2026-09-24 3:52 ` Damien Le Moal [this message]
2026-09-24 9:32 ` Niklas Cassel
2026-09-24 10:18 ` Matthias Goergens
2026-09-24 13:33 ` Niklas Cassel
2026-09-25 5:23 ` [PATCH v2] " Matthias Goergens
2026-09-25 9:18 ` Niklas Cassel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88fb216a-6024-49d2-97ae-79a1592541ff@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=matthias.goergens@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.