From: Qasim Ijaz <qasdev00@gmail.com>
To: ping.cheng@wacom.com, jason.gerecke@wacom.com, jikos@kernel.org,
bentiss@kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Qasim Ijaz <qasdev00@gmail.com>
Subject: [PATCH 0/3] HID: wacom: fix resource cleanup issues
Date: Wed, 30 Apr 2025 18:39:08 +0100 [thread overview]
Message-ID: <20250430173911.84705-1-qasdev00@gmail.com> (raw)
Fix a few resource cleanup issues.
Qasim Ijaz (3):
fix memory leak on kobject creation failure
fix memory leak on sysfs attribute creation failure
fix kobject reference count leak
drivers/hid/wacom_sys.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
2.39.5
next reply other threads:[~2025-04-30 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 17:39 Qasim Ijaz [this message]
2025-04-30 17:39 ` [PATCH 1/3] HID: wacom: fix memory leak on kobject creation failure Qasim Ijaz
2025-04-30 17:39 ` [PATCH 2/3] HID: wacom: fix memory leak on sysfs attribute " Qasim Ijaz
2025-04-30 17:39 ` [PATCH 3/3] HID: wacom: fix kobject reference count leak Qasim Ijaz
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=20250430173911.84705-1-qasdev00@gmail.com \
--to=qasdev00@gmail.com \
--cc=bentiss@kernel.org \
--cc=jason.gerecke@wacom.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ping.cheng@wacom.com \
/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;
as well as URLs for NNTP newsgroup(s).