Linux kernel -stable discussions
 help / color / mirror / Atom feed
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.11.2
Date: Fri, 26 Feb 2021 11:10:14 +0100	[thread overview]
Message-ID: <1614334214168@kroah.com> (raw)

I'm announcing the release of the 5.11.2 kernel.

All users of the 5.11 kernel series must upgrade.

The updated 5.11.y git tree can be found at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.11.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                                 |    2 -
 arch/arm64/boot/dts/nvidia/tegra210.dtsi |    1 
 arch/s390/pci/pci_mmio.c                 |    4 +--
 arch/x86/kvm/mmu/mmu.c                   |    2 -
 drivers/bluetooth/btusb.c                |    7 +++++
 drivers/hid/hid-core.c                   |    6 ++--
 drivers/hwmon/dell-smm-hwmon.c           |    7 +++++
 drivers/usb/core/quirks.c                |    9 ++++--
 fs/dax.c                                 |    5 ++-
 fs/ntfs/inode.c                          |    6 ++++
 include/linux/mm.h                       |    6 +++-
 kernel/bpf/verifier.c                    |   10 ++++---
 mm/memory.c                              |   41 +++++++++++++++++++++++++++----
 virt/kvm/kvm_main.c                      |   17 +++++++++---
 14 files changed, 96 insertions(+), 27 deletions(-)

Daniel Borkmann (1):
      bpf: Fix truncation handling for mod32 dst reg wrt zero

Greg Kroah-Hartman (1):
      Linux 5.11.2

Hui Wang (1):
      Bluetooth: btusb: Some Qualcomm Bluetooth adapters stop working

Johan Hovold (1):
      USB: quirks: sort quirk entries

Paolo Bonzini (2):
      KVM: do not assume PTE is writable after follow_pfn
      mm: provide a saner PTE walking API for modules

Rustam Kovhaev (1):
      ntfs: check for valid standard information attribute

Sameer Pujar (1):
      arm64: tegra: Add power-domain for Tegra210 HDA

Sean Christopherson (2):
      KVM: x86: Zap the oldest MMU pages, not the newest
      KVM: Use kvm_pfn_t for local PFN variable in hva_to_pfn_remapped()

Stefan Ursella (1):
      usb: quirks: add quirk to start video capture on ELMO L-12F document camera reliable

Thomas Hebb (1):
      hwmon: (dell-smm) Add XPS 15 L502X to fan control blacklist

Will McVicker (1):
      HID: make arrays usage and value to be the same


             reply	other threads:[~2021-02-26 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 10:10 Greg Kroah-Hartman [this message]
2021-02-26 10:10 ` Linux 5.11.2 Greg Kroah-Hartman
2021-02-26 10:54 ` Jörg-Volker Peetz
2021-02-26 11:02   ` Greg KH
2021-02-26 11:33     ` Jörg-Volker Peetz
2021-02-26 11:37       ` Jörg-Volker Peetz
2021-02-26 11:51         ` Jiri Slaby

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=1614334214168@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox