From: Ben Hutchings <ben@decadent.org.uk>
To: initramfs@vger.kernel.org, debian-kernel@lists.debian.org,
kernel-team@lists.ubuntu.com
Subject: initramfs-tools 0.134 release
Date: Sun, 28 Jul 2019 01:56:12 +0100 [thread overview]
Message-ID: <5c91947e2372cd93f0e7481c3e42ee352223dc1a.camel@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
This release fixes a number of bugs reported to Debian. It includes
more drivers in the initramfs that are needed by some ChromeOS devices.
It extends the autopkgtest static checks to cover all hooks and boot
scripts.
Ben.
Alper Nebi Yasak (2):
hook-functions: Include extcon-usbc-cros-ec when MODULES=most
hook-functions: Include extcon drivers when MODULES=dep
Ben Hutchings (14):
hooks/resume: Disable resume when there are no suitable swap devices
Merge branch 'master' into 'master'
Merge branch 'master' into 'master'
hook-functions: Include all keyboard driver modules when MODULES=most
hook-functions: Include cros_ec_spi and SPI drivers when MODULES=most
Merge branch 'ukl/bugfix-930754' into 'master'
resume: Set plymouth status only if there is a suspend image
hook-functions: Fix copy_file with target of "/bin"
scripts/functions: Use "reboot -f" to reboot on panic
unmkinitramfs: Work around lz4cat filename check
initramfs-tools-core: Depend on logsave or older e2fsprogs
update-initramfs(8): Document -d option as "delete" instead of "remove"
update-initramfs(8): Update description of "-k all" option
Releasing version 0.134.
Benjamin Drung (1):
autopkgtest: Check also /usr/share/initramfs-tools/{hooks,scripts}
Uwe Kleine-König (1):
mkinitramfs: suppress warning when using bzip2 or lzma
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2019-07-28 0:56 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=5c91947e2372cd93f0e7481c3e42ee352223dc1a.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=initramfs@vger.kernel.org \
--cc=kernel-team@lists.ubuntu.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).