From: Simon Horman <horms@kernel.org>
To: kexec@lists.infradead.org
Subject: [ANNOUNCE] kexec-tools 2.0.27-rc1
Date: Fri, 18 Aug 2023 12:49:02 +0200 [thread overview]
Message-ID: <ZN9MnhFyaAbcVzo3@vergenet.net> (raw)
Hi all,
I am happy to announce the release of kexec-tools 2.0.27-rc1.
This is an incremental feature pre-release.
So long as no serious problems arise I intend to release kexec-tools 2.0.27
in a weeks time. Testing of 2.0.27-rc1 would be greatly appreciated.
I do not have any outstanding changes for 2.0.27 at this time.
And I would like to only accept bug fixes at this time and take
features patches once 2.0.27 has been released.
The pre-release can be downloaded from kernel.org:
https://kernel.org/pub/linux/utils/kernel/kexec/kexec-tools-2.0.27-rc1.tar.xz
https://kernel.org/pub/linux/utils/kernel/kexec/
I have also tagged it in git:
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
Thanks to everyone who has contributed to kexec.
For reference the changes since v2.0.26 are:
777ca453ca69 kexec-tools 2.0.27-rc1
f67c4146d7b5 arm64: Hook up the ZBOOT support as vmlinuz
fc7b83bdf734 arm64: Add ZBOOT PE containing compressed image support
f41c4182b0c4 kexec/zboot: Add arch independent zboot support
1572b91da7c4 kexec: Introduce a member kernel_fd in kexec_info
714fa11590fe kexec/arm64: Simplify the code for zImage
a8de94e5f033 LoongArch: kdump: Set up kernel image segment
4203eaccfa92 kexec: __NR_kexec_file_load is set to undefined on LoongArch
63e9a012112e ppc64: Add elf-ppc64 file types/options and an arch specific flag to man page
806711fca9e9 x86: add devicetree support
29fe5067ed07 kexec: make -a the default
e63fefd4fc35 ppc64: add --reuse-cmdline parameter support
8fc55927f700 kexec-tools 2.0.26.git
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2023-08-18 10:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZN9MnhFyaAbcVzo3@vergenet.net \
--to=horms@kernel.org \
--cc=kexec@lists.infradead.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