From: Ismail Tarim <ismailtarim7@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: James Ogletree <jogletre@opensource.cirrus.com>,
Fred Treven <fred.treven@cirrus.com>,
Ben Bright <ben.bright@cirrus.com>,
patches@opensource.cirrus.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Input: cs40l50 - fix OWT upload length
Date: Tue, 17 Nov 2026 00:09:17 +0300 [thread overview]
Message-ID: <20261116210918.1940242-1-ismailtarim7@gmail.com> (raw)
In-Reply-To: <20261031095438.3070451-1-ismailtarim7@gmail.com>
Hi Dmitry,
Gentle ping on this two-patch series. Patch 1 fixes an out-of-bounds
read in cs40l50_upload_owt(), where regmap_bulk_write() gets a byte
count instead of a register count. Patch 2 fixes a work item leak in
the stop worker.
I can rebase or resend if that helps.
Thanks,
Ismail
prev parent reply other threads:[~2026-11-16 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 9:54 Ismail Tarim
2026-10-31 9:54 ` [PATCH 2/2] Input: cs40l50 - fix work item leak in stop worker Ismail Tarim
2026-11-16 21:09 ` Ismail Tarim [this message]
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=20261116210918.1940242-1-ismailtarim7@gmail.com \
--to=ismailtarim7@gmail.com \
--cc=ben.bright@cirrus.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fred.treven@cirrus.com \
--cc=jogletre@opensource.cirrus.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.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
all inboxes | Powered by JetHome®