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.10.57
Date: Sun, 8 Aug 2021 09:15:50 +0200 [thread overview]
Message-ID: <162840695072108@kroah.com> (raw)
I'm announcing the release of the 5.10.57 kernel.
All users of the 5.10 kernel series must upgrade.
The updated 5.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.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
drivers/firmware/arm_scmi/bus.c | 3
drivers/firmware/arm_scmi/driver.c | 8
drivers/firmware/efi/mokvar-table.c | 5
drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c | 6
drivers/gpu/drm/amd/display/dc/dml/dcn21/display_mode_vba_21.c | 2
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 164 ----------
drivers/gpu/drm/i915/i915_cmd_parser.c | 28 -
drivers/gpu/drm/i915/i915_request.c | 8
drivers/net/ethernet/qlogic/qed/qed_mcp.c | 23 +
drivers/net/usb/r8152.c | 3
drivers/nvme/host/trace.h | 6
drivers/regulator/rtmv20-regulator.c | 2
drivers/spi/spi-mt65xx.c | 19 -
drivers/spi/spi-stm32.c | 15
drivers/watchdog/iTCO_wdt.c | 12
fs/btrfs/tree-log.c | 5
include/acpi/acpi_bus.h | 3
include/linux/mfd/rt5033-private.h | 4
net/bluetooth/hci_core.c | 16
net/core/skbuff.c | 5
sound/soc/codecs/rt5682.c | 8
sound/soc/codecs/tlv320aic31xx.h | 4
sound/soc/ti/j721e-evm.c | 18 -
tools/testing/selftests/bpf/progs/bpf_iter_task.c | 3
tools/testing/selftests/bpf/test_verifier.c | 2
tools/testing/selftests/bpf/verifier/and.c | 2
tools/testing/selftests/bpf/verifier/basic_stack.c | 2
tools/testing/selftests/bpf/verifier/bounds.c | 19 -
tools/testing/selftests/bpf/verifier/bounds_deduction.c | 21 -
tools/testing/selftests/bpf/verifier/bounds_mix_sign_unsign.c | 13
tools/testing/selftests/bpf/verifier/calls.c | 4
tools/testing/selftests/bpf/verifier/const_or.c | 4
tools/testing/selftests/bpf/verifier/dead_code.c | 2
tools/testing/selftests/bpf/verifier/helper_access_var_len.c | 12
tools/testing/selftests/bpf/verifier/int_ptr.c | 6
tools/testing/selftests/bpf/verifier/jmp32.c | 22 +
tools/testing/selftests/bpf/verifier/jset.c | 10
tools/testing/selftests/bpf/verifier/map_ptr.c | 4
tools/testing/selftests/bpf/verifier/raw_stack.c | 10
tools/testing/selftests/bpf/verifier/stack_ptr.c | 22 -
tools/testing/selftests/bpf/verifier/unpriv.c | 9
tools/testing/selftests/bpf/verifier/value_ptr_arith.c | 17 -
tools/testing/selftests/bpf/verifier/var_off.c | 115 ++++++-
44 files changed, 332 insertions(+), 336 deletions(-)
Alain Volmat (1):
spi: stm32h7: fix full duplex irq handler handling
Andrei Matei (2):
selftest/bpf: Adjust expected verifier errors
selftest/bpf: Verifier tests for var-off access
Axel Lin (1):
regulator: rt5033: Fix n_voltages settings for BUCK and LDO
Borislav Petkov (1):
efi/mokvar: Reserve the table only if it is in boot services data
ChiYuan Huang (1):
regulator: rtmv20: Fix wrong mask for strobe-polarity-high
Cristian Marussi (1):
firmware: arm_scmi: Add delayed response status check
Daniel Borkmann (3):
bpf, selftests: Adjust few selftest result_unpriv outcomes
bpf: Update selftests to reflect new error states
bpf, selftests: Adjust few selftest outcomes wrt unreachable code
Filipe Manana (2):
btrfs: fix race causing unnecessary inode logging during link and rename
btrfs: fix lost inode on log replay after mix of fsync, rename and inode eviction
Greg Kroah-Hartman (3):
Revert "Bluetooth: Shutdown controller after workqueues are flushed or cancelled"
Revert "watchdog: iTCO_wdt: Account for rebooting on second timeout"
Linux 5.10.57
Guenter Roeck (1):
spi: mediatek: Fix fifo transfer
Jason Ekstrand (2):
drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser"
Revert "drm/i915: Propagate errors on awaiting already signaled fences"
Jia He (1):
qed: fix possible unpaired spin_{un}lock_bh in _qed_mcp_cmd_and_union()
Keith Busch (1):
nvme: fix nvme_setup_command metadata trace event
Kyle Russell (1):
ASoC: tlv320aic31xx: fix reversed bclk/wclk master bits
Linus Torvalds (1):
ACPI: fix NULL pointer dereference
Nicholas Kazlauskas (1):
drm/amd/display: Fix max vstartup calculation for modes with borders
Oder Chiou (1):
ASoC: rt5682: Fix the issue of garbled recording after powerd_dbus_suspend
Peter Ujfalusi (2):
ASoC: ti: j721e-evm: Fix unbalanced domain activity tracking during startup
ASoC: ti: j721e-evm: Check for not initialized parent_clk_id
Pravin B Shelar (1):
net: Fix zero-copy head len calculation.
Sudeep Holla (1):
firmware: arm_scmi: Ensure drivers provide a probe function
Takashi Iwai (1):
r8152: Fix potential PM refcount imbalance
Victor Lu (1):
drm/amd/display: Fix comparison error in dcn21 DML
Yonghong Song (1):
selftests/bpf: Add a test for ptr_to_map_value on stack for helper access
next reply other threads:[~2021-08-08 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 7:15 Greg Kroah-Hartman [this message]
2021-08-08 7:15 ` Linux 5.10.57 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=162840695072108@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.