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.8.7
Date: Sat, 5 Sep 2020 11:48:35 +0200 [thread overview]
Message-ID: <1599299316180106@kroah.com> (raw)
I'm announcing the release of the 5.8.7 kernel.
All users of the 5.8 kernel series must upgrade.
The updated 5.8.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.8.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
------------
Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt | 32 ++++
Makefile | 2
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 20 +--
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 15 +-
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 20 +--
arch/arm64/include/asm/kvm_asm.h | 43 ++++++
arch/arm64/kernel/vmlinux.lds.S | 8 +
arch/arm64/kvm/hyp/entry.S | 15 +-
arch/arm64/kvm/hyp/hyp-entry.S | 65 ++++++----
arch/arm64/kvm/hyp/switch.c | 39 +++++-
drivers/hid/hid-core.c | 15 ++
drivers/hid/hid-input.c | 4
drivers/hid/hid-multitouch.c | 2
drivers/media/v4l2-core/v4l2-ioctl.c | 50 ++++---
drivers/mmc/host/sdhci-tegra.c | 2
drivers/target/target_core_user.c | 11 +
include/linux/hid.h | 42 ++++--
mm/gup.c | 2
net/netfilter/nft_set_rbtree.c | 23 ++-
net/wireless/nl80211.c | 2
tools/perf/Documentation/perf-record.txt | 4
tools/perf/Documentation/perf-stat.txt | 4
tools/testing/selftests/x86/test_vsyscall.c | 22 +++
23 files changed, 325 insertions(+), 117 deletions(-)
Andy Lutomirski (1):
selftests/x86/test_vsyscall: Improve the process_vm_readv() test
Bodo Stroesser (1):
scsi: target: tcmu: Optimize use of flush_dcache_page
Dave Hansen (1):
mm: fix pin vs. gup mismatch with gate pages
Greg Kroah-Hartman (1):
Linux 5.8.7
James Morse (2):
KVM: arm64: Add kvm_extable for vaxorcism code
KVM: arm64: Survive synchronous exceptions caused by AT instructions
Johannes Berg (1):
nl80211: fix NL80211_ATTR_HE_6GHZ_CAPABILITY usage
Kim Phillips (1):
perf record/stat: Explicitly call out event modifiers in the documentation
Marc Zyngier (2):
HID: core: Correctly handle ReportSize being zero
HID: core: Sanitize event code and type when mapping input
Peilin Ye (1):
media: media/v4l2-core: Fix kernel-infoleak in video_put_user()
Sowjanya Komatineni (6):
dt-bindings: mmc: tegra: Add tmclk for Tegra210 and later
arm64: tegra: Add missing timeout clock to Tegra194 SDMMC nodes
arm64: tegra: Add missing timeout clock to Tegra186 SDMMC nodes
arm64: tegra: Add missing timeout clock to Tegra210 SDMMC
sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra210
sdhci: tegra: Remove SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK for Tegra186
Stefano Brivio (1):
netfilter: nft_set_rbtree: Handle outcomes of tree rotations in overlap detection
next reply other threads:[~2020-09-05 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 9:48 Greg Kroah-Hartman [this message]
2020-09-05 9:48 ` Linux 5.8.7 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=1599299316180106@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.