[PATCH] MAINTAINERS: name the livepatching for-next branch

[PATCH] MAINTAINERS: name the livepatching for-next branch

[Matthias Goergens]

The T: entry for LIVE PATCHING names livepatching/livepatching 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 the entry.

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 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 140eafcbbd78..e603835e4744 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -15160,7 +15160,7 @@ M:	Petr Mladek <pmladek@suse.com>
 R:	Joe Lawrence <joe.lawrence@redhat.com>
 L:	live-patching@vger.kernel.org
 S:	Maintained
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git for-next
 F:	Documentation/ABI/testing/sysfs-kernel-livepatch
 F:	Documentation/livepatch/
 F:	arch/powerpc/include/asm/livepatch.h

base-commit: 62f4c998b297cf233997a2b4cd6fc2d2df0319c9
-- 
2.55.0

Re: [PATCH] MAINTAINERS: name the livepatching for-next branch

[Petr Mladek]

On Sat 2026-09-26 13:52:19, Matthias Goergens wrote:
> The T: entry for LIVE PATCHING names livepatching/livepatching 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 the entry.
> 
> 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/

It seems that the motivation is that "master" is outdated in various
projects.

But I maintain livepatching/livepatching.git the following way:

  + "master" branch points to the last merge commit in Linus tree.

  + "linux-next" is based on "master" plus there are merged the "for-X-Y/*"
    development branches for the next merge window.

As a result, "master" and "linux-next" differ only by the few patches
which are in the queue for the next release. I believe that most
people actually sent patches based on the "master" branch because
they work with the Linus tree.

Note that livepatching is a pretty slowly moving subsystem.

By other worse, I believe that "master" is more appropriate for
livepatching.git.

Best Regards,
Petr

> diff --git a/MAINTAINERS b/MAINTAINERS
> index 140eafcbbd78..e603835e4744 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15160,7 +15160,7 @@ M:	Petr Mladek <pmladek@suse.com>
>  R:	Joe Lawrence <joe.lawrence@redhat.com>
>  L:	live-patching@vger.kernel.org
>  S:	Maintained
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git
> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git for-next
>  F:	Documentation/ABI/testing/sysfs-kernel-livepatch
>  F:	Documentation/livepatch/
>  F:	arch/powerpc/include/asm/livepatch.h
> 
> base-commit: 62f4c998b297cf233997a2b4cd6fc2d2df0319c9

Re: [PATCH] MAINTAINERS: name the livepatching for-next branch

[Miroslav Benes]

Hi,

On Tue, 29 Sep 2026, Petr Mladek wrote:

> On Sat 2026-09-26 13:52:19, Matthias Goergens wrote:
> > The T: entry for LIVE PATCHING names livepatching/livepatching 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 the entry.
> > 
> > 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/

what is the main motivation then? The changelog talks about linux-next but 
that would not be a good reason in my opinion. T: has a link to the repo, 
not to some arbitrary branch.

The thread above mentions Sashiko. Is that the issue then? Yes, it is 
sometimes annoying that Sashiko bases reviews on our master branch and 
disregards patches in for-next branch, but as Petr explains below it is 
not a serious issue in our tree. There is usually not much happening.

> It seems that the motivation is that "master" is outdated in various
> projects.
> 
> But I maintain livepatching/livepatching.git the following way:
> 
>   + "master" branch points to the last merge commit in Linus tree.
> 
>   + "linux-next" is based on "master" plus there are merged the "for-X-Y/*"
>     development branches for the next merge window.
> 
> As a result, "master" and "linux-next" differ only by the few patches
> which are in the queue for the next release. I believe that most
> people actually sent patches based on the "master" branch because
> they work with the Linus tree.
> 
> Note that livepatching is a pretty slowly moving subsystem.
> 
> By other worse, I believe that "master" is more appropriate for
> livepatching.git.

Agreed.

If it becomes a problem, we should consider 
https://korg.docs.kernel.org/gitolite/index.html#symbolic-ref as mentioned 
in the linked thread above.

Or perhaps have a specific pointer for Sashiko in MAINTAINERS file but 
that would be more involved.

Miroslav

Re: [PATCH] MAINTAINERS: name the livepatching for-next branch

[Matthias Goergens]

Hi Petr, Miroslav,

You're right: please drop this one, and sorry for the noise.

The motivation was Sashiko, as you guessed: it used to review against
the default branch of the tree in T:, which for some trees is far
behind what patches are based on.  Since 28 September it no longer does
that when mainline already contains the default branch; it falls back
to linux-next instead, which for livepatching already has the two
queued commits.  So the patch no longer buys you anything.

Thanks,
Matthias