From: Markus Elfring <Markus.Elfring@web.de>
To: Qasim Ijaz <qasdev00@gmail.com>, linux-input@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Jason Gerecke <jason.gerecke@wacom.com>,
Jiri Kosina <jikos@kernel.org>, Ping Cheng <ping.cheng@wacom.com>
Subject: Re: [PATCH] HID: wacom: fix memory leak on size mismatch in wacom_wac_queue_flush()
Date: Sat, 29 Mar 2025 13:04:05 +0100 [thread overview]
Message-ID: <94993789-8637-4b93-b30a-194e9078adcf@web.de> (raw)
In-Reply-To: <20250329002042.36967-1-qasdev00@gmail.com>
…
> number of elements it has copied. The code checks if the number
> of copied elements does not equal the size of the fifo record,
…
is?
Under which circumstances would you dare to use text lines
which would be longer than 63 characters?
Can a patch series be more appropriate for the affected software module?
Regards,
Markus
next prev parent reply other threads:[~2025-03-29 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 0:20 [PATCH] HID: wacom: fix memory leak on size mismatch in wacom_wac_queue_flush() Qasim Ijaz
2025-03-29 12:04 ` Markus Elfring [this message]
2025-04-01 15:21 ` Jason Gerecke
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=94993789-8637-4b93-b30a-194e9078adcf@web.de \
--to=markus.elfring@web.de \
--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 \
--cc=qasdev00@gmail.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