From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: [GIT PULL] Staging driver fixes for 6.18-rc3
Date: Sun, 26 Oct 2025 14:59:59 +0100 [thread overview]
Message-ID: <aP4pX6-QYmlmM27h@kroah.com> (raw)
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-6.18-rc3
for you to fetch changes up to b1aabb8ef09b4cf0cc0c92ca9dfd19482f3192c1:
staging: gpib: Fix device reference leak in fmh_gpib driver (2025-10-13 10:55:03 +0200)
----------------------------------------------------------------
staging driver fixes for 6.18-rc3
Here are some small staging driver fixes for the gpib subsystem to
resolve some reported issues. Included in here are:
- memory leak fixes
- error code fixes
- proper protocol fixes
All of these have been in linux-next for almost 2 weeks now with no
reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Dave Penkler (3):
staging: gpib: Fix no EOI on 1 and 2 byte writes
staging: gpib: Fix sending clear and trigger events
staging: gpib: Return -EINTR on device clear
Ma Ke (1):
staging: gpib: Fix device reference leak in fmh_gpib driver
drivers/staging/gpib/agilent_82350b/agilent_82350b.c | 12 +++++++-----
drivers/staging/gpib/fmh_gpib/fmh_gpib.c | 5 +++++
drivers/staging/gpib/ni_usb/ni_usb_gpib.c | 13 ++++++++++---
3 files changed, 22 insertions(+), 8 deletions(-)
next reply other threads:[~2025-10-26 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 13:59 Greg KH [this message]
2025-10-26 17:37 ` [GIT PULL] Staging driver fixes for 6.18-rc3 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=aP4pX6-QYmlmM27h@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--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