mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Mason <clm@meta.com>
To: Jonathan Cameron <jic23@kernel.org>,
	Tomas Melin <tomas.melin@vaisala.com>
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
	Nuno Sa <nuno.sa@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>,
	Olivier Moysan <olivier.moysan@foss.st.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 5/5] iio: adc: ad9467: check for backend capabilities
Date: Mon, 9 Feb 2026 09:37:33 -0500	[thread overview]
Message-ID: <86cb317f-1fdc-4250-bbf2-8ea670b34ca7@meta.com> (raw)
In-Reply-To: <20260208193034.7c780426@jic23-huawei>

On 2/8/26 2:30 PM, Jonathan Cameron wrote:
> On Thu, 05 Feb 2026 12:24:11 +0000
> Tomas Melin <tomas.melin@vaisala.com> wrote:
> 
>> Add capability checks for operation with backends that do not necessarily
>> support full set of features, but are otherwise compatible with the device.
>> This ensures a fully functional device, but with limited capabilities.
>>
>> Signed-off-by: Tomas Melin <tomas.melin@vaisala.com>
> I've mentioned before that I've started messing around with Chris Mason's
> set of Claude Code prompts and today I was trying out the new stuff mentioned in:
> https://lore.kernel.org/all/b187e0c1-1df8-4529-bfe4-0a1d65221adc@meta.com/ 
> 
> 
> Given this patch set is pretty much ready to merge I asked it to take a look
> and it came up with something that certainly merited me taking a look.
> 
>  Issue: In ad9467_chan_test_mode_write(), the testmode_on path is guarded
>   by IIO_BACKEND_CAP_CALIBRATION but the matching testmode_off path is not.
>   On backends without that capability, entering PN test mode succeeds but
>   exiting fails with -EOPNOTSUPP, leaving the ADC stuck in test mode.
> 
> I may be missing some protection path, but I think it is right and if you
> were to set up the test modes with a backend that doesn't support the
> relevant functionality you would indeed be able to turn them on but never
> off again.
> 
> So this might be the first bug in IIO that the LLM found and human's, including
> me, missed!  
> 
> Thanks Chris! I won't +CC you every time but wanted to acknowledge that your
> hard work taming these tools is very useful to me.

I'm really glad the AI reviews are helpful, please don't hesitate to
reach out with feature requests or buggy reviews.

Also, if you're using the prompts in CI, I try to keep the breaking
changes to a minimum, but I'll be refactoring things over the next few
weeks.  The entry points (kernel/review-core.md and kernel/agent/orc.md)
shouldn't change, but some of the other files might move around.

Please don't be shy if we're adding regressions for you, my goal is to
make these easy to consume.

-chris


  parent reply	other threads:[~2026-02-09 14:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 12:24 [PATCH v6 0/5] iio: adc: ad9467: Support alternative backends Tomas Melin
2026-02-05 12:24 ` [PATCH v6 1/5] iio: industrialio-backend: support backend capabilities Tomas Melin
2026-02-05 12:24 ` [PATCH v6 2/5] iio: adc: adi-axi-adc: define supported iio-backend capabilities Tomas Melin
2026-02-05 12:24 ` [PATCH v6 3/5] iio: dac: adi-axi-dac: " Tomas Melin
2026-02-05 12:24 ` [PATCH v6 4/5] iio: adc: sd_adc_modulator: " Tomas Melin
2026-02-05 12:24 ` [PATCH v6 5/5] iio: adc: ad9467: check for backend capabilities Tomas Melin
2026-02-05 16:34   ` Andy Shevchenko
2026-02-09  7:24     ` Tomas Melin
2026-02-09  8:41       ` Andy Shevchenko
2026-02-09 10:01         ` Tomas Melin
2026-02-09 10:35           ` Andy Shevchenko
2026-02-07 18:43   ` David Lechner
2026-02-08 19:30   ` Jonathan Cameron
2026-02-09  7:17     ` Tomas Melin
2026-02-09 14:19     ` Nuno Sá
2026-02-09 14:37     ` Chris Mason [this message]
2026-02-07 18:43 ` [PATCH v6 0/5] iio: adc: ad9467: Support alternative backends David Lechner
2026-02-08  9:05 ` Nuno Sá

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=86cb317f-1fdc-4250-bbf2-8ea670b34ca7@meta.com \
    --to=clm@meta.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=tomas.melin@vaisala.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

Powered by JetHome