From: Dave Penkler <dpenkler@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: Dave Penkler <dpenkler@gmail.com>
Subject: [PATCH 0/2] staging: gpib: Fix NULL deref and code cleanup
Date: Sat, 18 Jan 2025 15:50:44 +0100 [thread overview]
Message-ID: <20250118145046.12181-1-dpenkler@gmail.com> (raw)
Patch 1 Fixes a NULL dereference issue in the detach function
Patch 2 Removes useless code
Use kzalloc
Adds proper cleanup on failure exit in the attach function.
Minor messaging changes
Dave Penkler (2):
staging: gpib: Fix NULL pointer dereference in detach
staging: gpib: Agilent usb code cleanup
.../gpib/agilent_82357a/agilent_82357a.c | 88 ++++++++-----------
1 file changed, 37 insertions(+), 51 deletions(-)
--
2.47.1
next reply other threads:[~2025-01-18 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 14:50 Dave Penkler [this message]
2025-01-18 14:50 ` [PATCH 1/2] staging: gpib: Fix NULL pointer dereference in detach Dave Penkler
2025-01-18 15:36 ` Greg KH
2025-01-18 17:30 ` Dave Penkler
2025-01-20 6:42 ` Dan Carpenter
2025-01-18 14:50 ` [PATCH 2/2] staging: gpib: Agilent usb code cleanup Dave Penkler
2025-01-20 7:15 ` Dan Carpenter
2025-01-20 15:15 ` Dave Penkler
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=20250118145046.12181-1-dpenkler@gmail.com \
--to=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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