From: Petr Mladek <pmladek@suse.com>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the livepatching for-next branch
Date: Tue, 29 Sep 2026 11:07:25 +0200 [thread overview]
Message-ID: <art_zcXuSXahklz3@pathway.suse.cz> (raw)
In-Reply-To: <20260926055219.3678061-1-matthias.goergens@gmail.com>
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
next prev parent reply other threads:[~2026-09-29 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 5:52 [PATCH] MAINTAINERS: name the livepatching for-next branch Matthias Goergens
2026-09-29 9:07 ` Petr Mladek [this message]
2026-09-29 10:15 ` Miroslav Benes
2026-09-30 3:40 ` Matthias Goergens
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=art_zcXuSXahklz3@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=matthias.goergens@gmail.com \
--cc=mbenes@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox