From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fixes for 7.1-final
Date: Fri, 12 Jun 2026 12:31:18 +0200 [thread overview]
Message-ID: <aivf9iEUUm9rdW6h@kroah.com> (raw)
The following changes since commit e43ffb69e0438cddd72aaa30898b4dc446f664f8:
Linux 7.1-rc6 (2026-05-31 15:14:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-7.1-final
for you to fetch changes up to 07ebe87915d8accdaba20c4f88c5ae430fe62fbb:
misc: fastrpc: fix use-after-free race in fastrpc_map_create (2026-06-05 17:20:51 +0200)
----------------------------------------------------------------
Char/Misc driver fixes for 7.1-final
Here are some small driver fixes for 7.1-final to resolve some reported
issues. Included in here are:
- slimbus qcom driver bugfixes
- nvmem driver bugfixes
- fastrpc driver bugfixes
- stratix10 firmware driver bugfixes
All of these have been in linux-next for over a week with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Anandu Krishnan E (1):
misc: fastrpc: fix use-after-free of fastrpc_user in workqueue context
Andre Heider (1):
nvmem: layouts: onie-tlv: fix hang on unknown types
Bartosz Golaszewski (2):
nvmem: core: fix use-after-free bugs in error paths
slimbus: qcom-ngd-ctrl: fix OF node refcount
Bjorn Andersson (7):
slimbus: qcom-ngd-ctrl: Fix up platform_driver registration
slimbus: qcom-ngd-ctrl: Fix probe error path ordering
slimbus: qcom-ngd-ctrl: Correct PDR and SSR cleanup ownership
slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd
slimbus: qcom-ngd-ctrl: Initialize controller resources in controller
slimbus: qcom-ngd-ctrl: Balance pm_runtime enablement for NGD
slimbus: qcom-ngd-ctrl: Avoid ABBA on tx_lock/ctrl->lock
Dinh Nguyen (1):
firmware: stratix10-rsu: Fix NULL deref on rsu_send_msg() timeout in probe
Greg Kroah-Hartman (1):
Merge tag 'svc_fixes_for_v7.1' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux into char-misc-linus
Junrui Luo (1):
misc: fastrpc: fix DMA address corruption due to find_vma misuse
Muhammad Amirul Asyraf Mohamad Jamian (2):
firmware: stratix10-svc: Return -EOPNOTSUPP when ATF async unsupported
firmware: stratix10-svc: Don't fail probe when async ops unsupported
Mukesh Ojha (1):
misc: fastrpc: Fix NULL pointer dereference in rpmsg callback
Zhenghang Xiao (1):
misc: fastrpc: fix use-after-free race in fastrpc_map_create
drivers/firmware/stratix10-rsu.c | 45 +++++++--------
drivers/firmware/stratix10-svc.c | 21 +++++--
drivers/misc/fastrpc.c | 107 +++++++++++++++++++++-------------
drivers/nvmem/core.c | 12 ++--
drivers/nvmem/layouts/onie-tlv.c | 3 +-
drivers/slimbus/qcom-ngd-ctrl.c | 122 ++++++++++++++++++++++++---------------
6 files changed, 189 insertions(+), 121 deletions(-)
next reply other threads:[~2026-06-12 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 10:31 Greg KH [this message]
2026-06-12 17:36 ` pr-tracker-bot
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=aivf9iEUUm9rdW6h@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@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
Powered by JetHome