From: Triet Hoang <triet.hoang.dev@gmail.com>
To: andi.shyti@kernel.org
Cc: bence98@sch.bme.hu, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, triet.hoang.dev@gmail.com
Subject: Re: [PATCH] i2c: cp2615: Validate read length before copying
Date: Thu, 20 Aug 2026 15:40:41 +0000 [thread overview]
Message-ID: <20260820154041.5911-1-triet.hoang.dev@gmail.com> (raw)
In-Reply-To: <aoYYzhB7Ia6cTTY0@zenone.zhora.eu>
On Thu, 20 Aug 2026 10:28:22 -0500, Andi wrote
> have you experienced any issue yourself or are you just
> speculating based on the code?
Hi Andi,
Thanks for replying. I just speculating based on the code.
BR,
Triet
prev parent reply other threads:[~2026-08-20 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 12:47 [PATCH] i2c: cp2615: Validate read length before copying Triet Hoang
2026-08-19 8:16 ` Markus Elfring
2026-08-20 11:57 ` Andi Shyti
2026-08-20 15:40 ` Triet Hoang [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=20260820154041.5911-1-triet.hoang.dev@gmail.com \
--to=triet.hoang.dev@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=bence98@sch.bme.hu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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