[PATCH] MAINTAINERS: name the robh/linux for-next branch

[PATCH] MAINTAINERS: name the robh/linux for-next branch

[Matthias Goergens]

The T: entries for OPEN FIRMWARE AND FLATTENED DEVICE TREE and OPEN
FIRMWARE AND FLATTENED DEVICE TREE BINDINGS name robh/linux without a
branch.  The repository's HEAD points to branch master, which mainline
already contains.  linux-next merges the for-next branch of this
repository (Next/Trees).  Name that branch in both entries.

Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
---
This is part of a cleanup of all T: entries whose repository HEAD is
not where development happens: one patch per repository, sent in small
batches.  The plan is at [1], and why it goes out in batches at [2].

[1] https://lore.kernel.org/all/20260924033200.3615554-1-matthias.goergens@gmail.com/
[2] https://lore.kernel.org/all/20260924101844.2403008-1-matthias.goergens@gmail.com/

 MAINTAINERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 140eafcbbd78..94f6c1278c16 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20449,7 +20449,7 @@ Q:	http://patchwork.kernel.org/project/devicetree/list/
 W:	http://www.devicetree.org/
 C:	irc://irc.libera.chat/devicetree
 P:	Documentation/process/maintainer-devicetree.rst
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
 F:	Documentation/ABI/testing/sysfs-firmware-ofw
 F:	drivers/of/
 F:	include/linux/of*.h
@@ -20471,7 +20471,7 @@ S:	Maintained
 Q:	http://patchwork.kernel.org/project/devicetree/list/
 C:	irc://irc.libera.chat/devicetree
 P:	Documentation/process/maintainer-devicetree.rst
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
 F:	Documentation/devicetree/
 F:	Documentation/process/maintainer-devicetree.rst
 F:	arch/*/boot/dts/

base-commit: 62f4c998b297cf233997a2b4cd6fc2d2df0319c9
-- 
2.55.0

Re: [PATCH] MAINTAINERS: name the robh/linux for-next branch

[Rob Herring]

On Mon, Sep 28, 2026 at 5:59 AM Matthias Goergens
<matthias.goergens@gmail.com> wrote:
>
> The T: entries for OPEN FIRMWARE AND FLATTENED DEVICE TREE and OPEN
> FIRMWARE AND FLATTENED DEVICE TREE BINDINGS name robh/linux without a
> branch.  The repository's HEAD points to branch master, which mainline
> already contains.  linux-next merges the for-next branch of this
> repository (Next/Trees).  Name that branch in both entries.
>
> Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
> ---
> This is part of a cleanup of all T: entries whose repository HEAD is
> not where development happens: one patch per repository, sent in small
> batches.  The plan is at [1], and why it goes out in batches at [2].

Is doing this preferred over changing what HEAD points to? Happy to do either.

Rob

Re: [PATCH] MAINTAINERS: name the robh/linux for-next branch

[Matthias Goergens]

Hi Rob,

> Is doing this preferred over changing what HEAD points to? Happy to do either.

Neither, it turns out; please drop the patch and leave HEAD as it is.

The motivation was Sashiko, which reviewed against the default branch
of the tree in T: even when that branch was far behind.  Your master
follows mainline closely; while it is at the same commit, as it is
today, Sashiko reviews against mainline in effect.  When it falls
behind, Sashiko now skips it (since 28 September) and uses linux-next,
which has your for-next and dt/linus.  As Greg pointed out on the tty
patch, a single branch in T: could not cover both anyway.  So there
is nothing for you to change.

Thanks,
Matthias

Re: [PATCH] MAINTAINERS: name the robh/linux for-next branch

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

On Thu, Oct 01, 2026 at 07:25:26PM +0800, Matthias Goergens wrote:
> Hi Rob,
> 
> > Is doing this preferred over changing what HEAD points to? Happy to do either.
> 
> Neither, it turns out; please drop the patch and leave HEAD as it is.
> 
> The motivation was Sashiko, which reviewed against the default branch
> of the tree in T: even when that branch was far behind.  Your master
> follows mainline closely; while it is at the same commit, as it is
> today, Sashiko reviews against mainline in effect.  When it falls
> behind, Sashiko now skips it (since 28 September) and uses linux-next,
> which has your for-next and dt/linus.  As Greg pointed out on the tty
> patch, a single branch in T: could not cover both anyway.  So there
> is nothing for you to change.

Does this mean that you're dropping and/or reverting all patches of this
kind?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH] MAINTAINERS: name the robh/linux for-next branch

[Matthias Goergens]

Hi Conor,

> Does this mean that you're dropping and/or reverting all patches of this
> kind?

Not reverting: the few that maintainers have already applied stay,
since they chose to take them.  I am dropping the ones where the
maintainer said a single branch does not fit their tree, like this one,
and I am not sending any more of them.

Matthias