From: Mike Rapoport <rppt@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
linux-next@vger.kernel.org
Subject: adding liveupdate tree to linux-next
Date: Thu, 16 Apr 2026 14:17:09 +0300 [thread overview]
Message-ID: <aeDFNb2skxuNrDIW@kernel.org> (raw)
Hi Mark,
We've setup a tree for Kexec HandOver/Live Update work and we are starting
to take KHO/LUO and kexec/kdump patches via that tree.
Can you please add our branches to linux-next?
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#fixes
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#next
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#kexec-fixes
https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git#kexec-next
--
Sincerely yours,
Mike.
next reply other threads:[~2026-04-16 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 11:17 Mike Rapoport [this message]
2026-04-16 11:46 ` adding liveupdate tree to linux-next Mark Brown
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=aeDFNb2skxuNrDIW@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
/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