[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a3b6fc8393a8a07a7ff2359380c25ff42fffcf7.camel@gmail.com>
Date: Mon, 04 Dec 2023 17:24:10 +0100
From: Nuno Sá <noname.nuno@...il.com>
To: Jonathan Cameron <jic23@...nel.org>,
Nuno Sa via B4 Relay
<devnull+nuno.sa.analog.com@...nel.org>
Cc: nuno.sa@...log.com, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-iio@...r.kernel.org,
Olivier MOYSAN <olivier.moysan@...s.st.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Lars-Peter Clausen <lars@...afoo.de>,
Michael Hennerich <Michael.Hennerich@...log.com>
Subject: Re: [PATCH 09/12] iio: adc: ad9467: use chip_info variables instead
of array
On Mon, 2023-12-04 at 15:25 +0000, Jonathan Cameron wrote:
> On Tue, 21 Nov 2023 11:20:22 +0100
> Nuno Sa via B4 Relay <devnull+nuno.sa.analog.com@...nel.org> wrote:
>
> > From: Nuno Sa <nuno.sa@...log.com>
> >
> > Instead of having an array and keeping IDs for each entry of the array,
> > just have a chip_info struct per device.
> >
> > Signed-off-by: Nuno Sa <nuno.sa@...log.com>
> Hi Nuno,
>
> Probably makes sense to break out the various tidy up an fixes for ad9467 as a
> precursor series and just refer to it from the main one (which will probably take
> longer to settle). Hopefully we can get these out the way and remove the
> distraction
> from the stuff you really care about!
>
> Jonathan
Alright... will do that!
- Nuno Sá
Powered by blists - more mailing lists