All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Tuna Kılıç" <tuna@tunakilic.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH] iio: dac: mcp47a1: Allow full-scale output
Date: Sun, 6 Sep 2026 22:49:28 +0100	[thread overview]
Message-ID: <20260906224928.4e24cb8b@jic23-huawei> (raw)
In-Reply-To: <20260906214420.580dec27@systembl0wer>

On Sun, 6 Sep 2026 21:44:20 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:

> On Sun, 6 Sep 2026 18:59:42 +0100
> Jonathan Cameron <jic23@kernel.org> wrote:
> 
> > On Sun,  6 Sep 2026 09:08:06 +0000 (UTC)
> > Tuna Kılıç <tuna@tunakilic.com> wrote:
> >   
> > > > If AI had anything much to do with generating the patch then
> > > > a tag for Assisted-by: LLM is appropriate.      
> > > 
> > > AI was only used afterwards as a sanity check for the datasheet,
> > > in_range() semantics, and the final patch. The bug and fix came from
> > > manual review.    
> > Ah fair enough then to not add a tag.
> > 
> > Thanks,
> > 
> > Jonathan
> >   
> > > 
> > > Thanks,
> > > Tuna    
> >   
> 
> Hi all,
> 
> sorry for the testing delay, did some light travelling this weekend
> and didn't have the hardware with me.
> 
> Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
> Tested-by: Joshua Crofts <joshua.crofts1@gmail.com>
No problem at all!   Thanks for following up.
Patch applied and marked for stable.

Thanks,

Jonathan

> 


  reply	other threads:[~2026-09-06 21:49 UTC|newest]

Thread overview: 9+ 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ıç
2026-09-06  3:54     ` Jonathan Cameron
2026-09-06  9:08       ` Tuna Kılıç
2026-09-06 17:59         ` Jonathan Cameron
2026-09-06 19:44           ` Joshua Crofts
2026-09-06 21:49             ` Jonathan Cameron [this message]
     [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=20260906224928.4e24cb8b@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=joshua.crofts1@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=tuna@tunakilic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.