From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Linux 5.4.173
Date: Thu, 20 Jan 2022 09:47:42 +0100 [thread overview]
Message-ID: <164266846389242@kroah.com> (raw)
I'm announcing the release of the 5.4.173 kernel.
All users of the 5.4 kernel series must upgrade.
The updated 5.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.4.y
and can be browsed at the normal kernel.org git web browser:
https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
thanks,
greg k-h
------------
Makefile | 4 +-
arch/arm/kernel/perf_callchain.c | 17 +++++++----
arch/arm/mm/Kconfig | 1
arch/arm64/kernel/perf_callchain.c | 18 ++++++++----
arch/csky/kernel/perf_callchain.c | 6 ++--
arch/nds32/kernel/perf_event_cpu.c | 17 +++++++----
arch/riscv/kernel/perf_callchain.c | 7 +++-
arch/s390/kvm/interrupt.c | 7 ++++
arch/s390/kvm/kvm-s390.c | 9 ++++--
arch/s390/kvm/kvm-s390.h | 1
arch/s390/kvm/sigp.c | 28 ++++++++++++++++++
arch/x86/events/core.c | 17 +++++++----
arch/x86/events/intel/core.c | 9 ++++--
arch/x86/kvm/x86.c | 2 -
drivers/base/devtmpfs.c | 8 +++++
drivers/firmware/qemu_fw_cfg.c | 20 +++++--------
drivers/media/usb/uvc/uvc_video.c | 4 ++
drivers/mtd/chips/Kconfig | 2 +
drivers/mtd/maps/Kconfig | 2 -
drivers/net/wireless/realtek/rtlwifi/rtl8192cu/hw.c | 1
fs/fs_context.c | 2 -
fs/orangefs/orangefs-bufmap.c | 7 ++--
fs/super.c | 4 +-
include/linux/fs_context.h | 2 +
include/linux/perf_event.h | 13 ++++++++
kernel/events/core.c | 13 ++++++--
sound/pci/hda/patch_realtek.c | 30 +++++++++++++++++++-
27 files changed, 190 insertions(+), 61 deletions(-)
Arnd Bergmann (1):
mtd: fixup CFI on ixp4xx
Christian Lachner (1):
ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after reboot from Windows
Christophe JAILLET (1):
orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
Eric Farman (1):
KVM: s390: Clarify SIGP orders versus STOP/RESTART
Greg Kroah-Hartman (1):
Linux 5.4.173
Jamie Hill-Daniel (1):
vfs: fs_context: fix up param length parsing in legacy_parse_param
Johan Hovold (4):
media: uvcvideo: fix division by zero at stream start
firmware: qemu_fw_cfg: fix sysfs information leak
firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
firmware: qemu_fw_cfg: fix kobject leak in probe error path
Larry Finger (1):
rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with interrupts enabled
Nathan Chancellor (1):
kbuild: Add $(KBUILD_HOSTLDFLAGS) to 'has_libelf' test
NeilBrown (1):
devtmpfs regression fix: reconfigure on each mount
Nick Desaulniers (1):
ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
Sean Christopherson (1):
perf: Protect perf_guest_cbs with RCU
Wei Wang (1):
KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
next reply other threads:[~2022-01-20 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 8:47 Greg Kroah-Hartman [this message]
2022-01-20 8:47 ` Linux 5.4.173 Greg Kroah-Hartman
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=164266846389242@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.