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.15.18
Date: Sat, 29 Jan 2022 11:59:55 +0100 [thread overview]
Message-ID: <1643453996204137@kroah.com> (raw)
I'm announcing the release of the 5.15.18 kernel.
All users of the 5.15 kernel series must upgrade.
The updated 5.15.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.15.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/include/asm/extable.h | 9 -
arch/arm64/include/asm/memory.h | 5
arch/arm64/kernel/traps.c | 2
arch/arm64/mm/extable.c | 13 +
arch/arm64/mm/ptdump.c | 2
arch/arm64/net/bpf_jit_comp.c | 7 -
drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 14 +-
drivers/gpu/drm/amd/display/dc/clk_mgr/dcn31/dcn31_smu.c | 6
drivers/gpu/drm/i915/gem/i915_gem_object_types.h | 1
drivers/gpu/drm/i915/gem/i915_gem_pages.c | 10 +
drivers/gpu/drm/i915/gt/intel_gt.c | 102 +++++++++++++++
drivers/gpu/drm/i915/gt/intel_gt.h | 2
drivers/gpu/drm/i915/gt/intel_gt_types.h | 2
drivers/gpu/drm/i915/i915_reg.h | 11 +
drivers/gpu/drm/i915/i915_vma.c | 3
drivers/gpu/drm/i915/intel_uncore.c | 26 +++
drivers/gpu/drm/i915/intel_uncore.h | 2
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 5
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 33 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 2
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 2
drivers/net/ethernet/broadcom/bnx2x/bnx2x.h | 11 +
drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 6
drivers/net/ethernet/broadcom/bnx2x/bnx2x_fw_defs.h | 2
drivers/net/ethernet/broadcom/bnx2x/bnx2x_hsi.h | 3
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 75 +++++++----
drivers/net/ethernet/broadcom/bnx2x/bnx2x_sriov.c | 13 +
fs/io_uring.c | 34 +++--
fs/select.c | 63 ++++-----
kernel/rcu/tree.c | 7 -
mm/memcontrol.c | 99 ++++++++++----
32 files changed, 416 insertions(+), 158 deletions(-)
Greg Kroah-Hartman (1):
Linux 5.15.18
Harry Wentland (1):
drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
Jan Kara (1):
select: Fix indefinitely sleeping task in poll_schedule_timeout()
Manish Chopra (2):
bnx2x: Utilize firmware 7.13.21.0
bnx2x: Invalidate fastpath HSI version for VFs
Mario Limonciello (1):
drm/amd/display: reset dcn31 SMU mailbox on failures
Mathias Krause (1):
drm/vmwgfx: Fix stale file descriptors on failed usercopy
Paul E. McKenney (1):
rcu: Tighten rcu_advance_cbs_nowake() checks
Pavel Begunkov (1):
io_uring: fix not released cached task refs
Russell King (1):
arm64/bpf: Remove 128MB limit for BPF JIT programs
Shakeel Butt (3):
memcg: flush stats only if updated
memcg: unify memcg stat flushing
memcg: better bounds on the memcg stats updates
Tvrtko Ursulin (1):
drm/i915: Flush TLBs before releasing backing store
next reply other threads:[~2022-01-29 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 10:59 Greg Kroah-Hartman [this message]
2022-01-29 10:59 ` Linux 5.15.18 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=1643453996204137@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;
as well as URLs for NNTP newsgroup(s).