From: Petr Mladek <pmladek@suse•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Jiri Kosina <jikos@kernel•org>,
Josh Poimboeuf <jpoimboe@kernel•org>,
Miroslav Benes <mbenes@suse•cz>,
Joe Lawrence <joe.lawrence@redhat•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: please clean up the livepatching tree
Date: Mon, 18 Aug 2025 12:32:55 +0200 [thread overview]
Message-ID: <aKMBV6LfqCYw1wQm@pathway.suse.cz> (raw)
In-Reply-To: <20250818121456.378af88b@canb.auug.org.au>
Hi Stephen,
On Mon 2025-08-18 12:14:56, Stephen Rothwell wrote:
> Hi all,
>
> The livepatching tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching
> branch for-next) only contains 70 merge commits and appears to not have
> been updated since March.
Just to be sure. What is exactly the problem, the merge commits or
that it has not been updated since March, please?
I have just removed the merge commits.
And there have not been any changes ready for the livepatching core code
recently.
Best Regards,
Petr
next prev parent reply other threads:[~2025-08-18 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:14 linux-next: please clean up the livepatching tree Stephen Rothwell
2025-08-18 10:32 ` Petr Mladek [this message]
2025-08-18 14:00 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2016-08-02 23:31 Stephen Rothwell
2016-08-02 23:41 ` Jiri Kosina
2016-08-03 1:23 ` Stephen Rothwell
2016-08-03 9:29 ` Jiri Kosina
2016-08-05 7:08 ` Takashi Iwai
2016-08-05 13:11 ` Jiri Kosina
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=aKMBV6LfqCYw1wQm@pathway.suse.cz \
--to=pmladek@suse$(echo .)com \
--cc=jikos@kernel$(echo .)org \
--cc=joe.lawrence@redhat$(echo .)com \
--cc=jpoimboe@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mbenes@suse$(echo .)cz \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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