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.2-rc5
Date: Sun, 26 Jul 2026 15:02:00 +0200 [thread overview]
Message-ID: <amYFSOB96efqLME4@kroah.com> (raw)
The following changes since commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa:
Linux 7.2-rc3 (2026-07-12 14:16:39 -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.2-rc5
for you to fetch changes up to 6e8c279f93dba93f42be7c9c6995bc8e318ba2e4:
MAINTAINERS: Update wine-devel list address (2026-07-17 16:05:34 +0200)
----------------------------------------------------------------
Char/Misc driver fixes for 7.2-rc5
Here are a number of small char/misc/etc. driver fixes for 7.2-rc5 that
resolve a bunch of different reported issues. Included in here are:
- rust_binder error message reporting fix
- stratix10-svc firmware driver fixes
- mei driver fix
- intel_th hardware tracing driver fix
- comedi driver fix
- uio_hv_generic driver fix
- ntsync selftest fix
- nsm misc driver fix
- some MAINTAINER file updates
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>
----------------------------------------------------------------
Adrian Ng Ho Yin (2):
firmware: stratix10-svc: handle NO_RESPONSE in async poll
firmware: stratix10-svc: fix teardown order in remove to prevent race
Alexander Usyskin (1):
mei: bus: access mei_device under device_lock on cleanup
Alice Ryhl (1):
rust_binder: only print failure if error has source
Ben Hutchings (1):
uio_hv_generic: Bind to FCopy device by default
Dave Penkler (1):
MAINTAINERS: Add Greg Kroah-Hartman to GPIB
Elizabeth Figura (1):
MAINTAINERS: Update wine-devel list address
Ethan Nelson-Moore (1):
selftests: ntsync: correct CONFIG_NTSYNC name
Genevieve Chan (1):
firmware: stratix10-svc: fix FCS SMC call kernel-doc
Greg Kroah-Hartman (1):
Merge tag 'svc_fixes_for_v7.2' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux into char-misc-linus
Guangshuo Li (1):
intel_th: fix MSC output device reference leak
Ian Abbott (1):
comedi: comedi_parport: deal with premature interrupt
Runyu Xiao (1):
misc: nsm: only unlock nsm_dev on post-lock error paths
Tze Yee Ng (1):
firmware: stratix10-svc: fix memory leaks and list corruption bugs
Xu Rao (1):
misc: nsm: pin the module while the device is open
MAINTAINERS | 3 ++-
drivers/android/binder/thread.rs | 14 +++++++-------
drivers/comedi/drivers/comedi_parport.c | 13 ++++++++++---
drivers/firmware/stratix10-svc.c | 19 +++++++++++--------
drivers/hwtracing/intel_th/core.c | 10 ----------
drivers/hwtracing/intel_th/msu.c | 2 ++
drivers/misc/mei/bus.c | 16 +++++++++-------
drivers/misc/nsm.c | 3 ++-
drivers/uio/uio_hv_generic.c | 8 +++++++-
include/linux/firmware/intel/stratix10-smc.h | 16 +++++++++++-----
tools/testing/selftests/drivers/ntsync/config | 2 +-
11 files changed, 62 insertions(+), 44 deletions(-)
reply other threads:[~2026-07-26 13:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=amYFSOB96efqLME4@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