From: "Tuna Kılıç" <tuna@tunakilic.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: dac: mcp47a1: Allow full-scale output
Date: Fri, 4 Sep 2026 12:51:04 +0000 (UTC) [thread overview]
Message-ID: <20260904125100.185128-1-tuna@tunakilic.com> (raw)
In-Reply-To: <20260904143848.00000d7d@gmail.com>
On Fri, Sep 4, 2026 at 2:38 PM Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> Can I ask how this was found? Manual code analysis or AI?
I noticed it while reviewing the driver's range handling and then
compared it with the MCP47A1 datasheet. AI was used as an aid during
the analysis, but I manually verified the datasheet values, in_range()
semantics, and the final patch before sending it.
I don't have MCP47A1 hardware available, so the testing was limited to
build and static checks.
Thanks,
Tuna
next prev parent reply other threads:[~2026-09-04 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 12:25 [PATCH] iio: dac: mcp47a1: Allow full-scale output Tuna Kılıç
2026-09-04 12:38 ` Joshua Crofts
2026-09-04 12:51 ` Tuna Kılıç [this message]
2026-09-06 3:54 ` Jonathan Cameron
2026-09-06 9:08 ` Tuna Kılıç
[not found] ` <1788525776688344002.1788525776@tunakilic.com>
2026-09-04 13:03 ` Joshua Crofts
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=20260904125100.185128-1-tuna@tunakilic.com \
--to=tuna@tunakilic.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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