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 6.2.2
Date: Fri, 3 Mar 2023 12:24:04 +0100 [thread overview]
Message-ID: <167784264418990@kroah.com> (raw)
I'm announcing the release of the 6.2.2 kernel.
All users of the 6.2 kernel series must upgrade.
The updated 6.2.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.2.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/socionext/uniphier-pxs3-ref-gadget0.dts | 2
arch/arm64/boot/dts/socionext/uniphier-pxs3-ref-gadget1.dts | 2
arch/arm64/crypto/sm4-ce-gcm-glue.c | 51 +++++-------
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3
drivers/gpu/drm/amd/display/dc/dcn314/dcn314_hwseq.c | 24 +++++
drivers/gpu/drm/amd/display/dc/dcn314/dcn314_hwseq.h | 2
drivers/gpu/drm/amd/display/dc/dcn314/dcn314_init.c | 2
drivers/gpu/drm/amd/display/dmub/inc/dmub_cmd.h | 25 +++++
drivers/net/wireless/realtek/rtw88/usb.c | 18 ----
drivers/tty/vt/vc_screen.c | 7 -
drivers/usb/core/hub.c | 5 -
drivers/usb/core/sysfs.c | 5 -
drivers/usb/dwc3/dwc3-pci.c | 4
drivers/usb/gadget/function/u_serial.c | 23 ++++-
drivers/usb/serial/option.c | 4
drivers/usb/typec/pd.c | 1
net/core/filter.c | 4
scripts/tags.sh | 2
sound/pci/hda/hda_cs_dsp_ctl.c | 4
20 files changed, 124 insertions(+), 66 deletions(-)
Alan Stern (1):
USB: core: Don't hold device lock while reading the "descriptors" sysfs file
Carlos Llamas (1):
scripts/tags.sh: fix incompatibility with PCRE2
Florian Zumbiehl (1):
USB: serial: option: add support for VW/Skoda "Carstick LTE"
Greg Kroah-Hartman (1):
Linux 6.2.2
Heikki Krogerus (1):
usb: dwc3: pci: add support for the Intel Meteor Lake-M
Herbert Xu (1):
crypto: arm64/sm4-gcm - Fix possible crash in GCM cryption
Kunihiko Hayashi (1):
arm64: dts: uniphier: Fix property name in PXs3 USB node
Martin KaFai Lau (1):
bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state
Nicholas Kazlauskas (1):
drm/amd/display: Move DCN314 DOMAIN power control to DMCUB
Prashanth K (1):
usb: gadget: u_serial: Add null pointer check in gserial_resume
Saranya Gopal (1):
usb: typec: pd: Remove usb_suspend_supported sysfs from sink PDO
Sascha Hauer (3):
wifi: rtw88: usb: Set qsel correctly
wifi: rtw88: usb: send Zero length packets if necessary
wifi: rtw88: usb: drop now unnecessary URB size check
Stylon Wang (1):
drm/amd/display: Properly reuse completion structure
Thomas Weißschuh (1):
vc_screen: don't clobber return value in vcs_read
Vitaly Rodionov (1):
ALSA: hda: cs35l41: Correct error condition handling
next reply other threads:[~2023-03-03 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 11:24 Greg Kroah-Hartman [this message]
2023-03-03 11:24 ` Linux 6.2.2 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=167784264418990@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