From: Simon Horman <horms@verge.net.au>
To: kexec@lists.infradead.org
Subject: [ANNOUNCE] kexec-tools 2.0.23
Date: Thu, 4 Nov 2021 16:07:46 +0100 [thread overview]
Message-ID: <20211104150746.GA2452@vergenet.net> (raw)
Hi all,
I am happy to announce the release of kexec-tools 2.0.22.
This is a feature release coinciding with the release of v5.12
of the Linux Kernel.
This release can be downloaded from kernel.org:
http://kernel.org/pub/linux/utils/kernel/kexec/kexec-tools-2.0.23.tar.xz
http://kernel.org/pub/linux/utils/kernel/kexec/
It is also tagged it in git:
git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
Thanks to everyone who has contributed to kexec!
Commits since v2.0.22:
91ff1e7 kexec-tools 2.0.23
41725a0 kexec-tools 2.0.23-rc1
5f8d632 arm: kdump: Add DT properties to crash dump kernel's DTB
bb1c95c kexec-tools: multiboot2: Correct BASIC_MEMINFO memory units
a4d49e8 Add some necessary free() calls
bcee4f2 Add some necessary fclose() calls
84ef6cb ppc64: Fix memory leak problem in zImage_ppc64_load()
35dec3d i386: Remove unused local variable in get_kernel_page_offset()
dbc151e multiboot2: Accept x86-64 images
e388195 multiboot2: Avoid first 0x500 bytes
1d02758 multiboot2: Use rel_min and rel_max for buffer destinations
4f8d667 multiboot2: Correct MBI size calculation
bfaebfb x86: Consolidate elf_x86_probe routines
091f9e9 Refer FDT tokens with symbolic names
61b8c79 arm64/crashdump-arm64: deduce the paddr of _text
5e7ce27 kexec-tools: Remove duplicate definition of ramdisk
a2ba3cd kexec-tools 2.0.21.git
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2021-11-04 15:08 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=20211104150746.GA2452@vergenet.net \
--to=horms@verge.net.au \
--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