From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "David Marinović" <david.marinovic@pupin.rs>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
michael.hennerich@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] iio: dac: ltc2632: drop enum and use individual chip_info objects
Date: Wed, 18 Mar 2026 16:57:08 +0200 [thread overview]
Message-ID: <abq9RCfFjGVzhrMg@ashevche-desk.local> (raw)
In-Reply-To: <20260318135736.91564-2-david.marinovic@pupin.rs>
On Wed, Mar 18, 2026 at 02:57:30PM +0100, David Marinović wrote:
> Remove the ltc2632_chip_info_tbl[] array and related
> ltc2632_supported_device_ids enum used for looking up chip-specific
> information. Instead, use separate static const struct
> ltc2632_chip_info objects for each supported chip variant.
Suggested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
(I have not reviewed that scrupulously, but at the brief look for the values
and names LGTM.)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-18 14:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 15:27 [PATCH 0/2] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-10 15:29 ` [PATCH 1/2] " David Marinović
2026-03-11 12:18 ` Andy Shevchenko
2026-03-10 15:32 ` [PATCH 2/2] dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings David Marinović
2026-03-11 13:03 ` Krzysztof Kozlowski
2026-03-11 13:04 ` Krzysztof Kozlowski
2026-03-18 13:57 ` [PATCH v2 0/3] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-18 13:57 ` [PATCH 1/3] iio: dac: ltc2632: drop enum and use individual chip_info objects David Marinović
2026-03-18 14:57 ` Andy Shevchenko [this message]
2026-03-18 13:57 ` [PATCH 2/3] dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings David Marinović
2026-03-18 17:38 ` Conor Dooley
2026-03-18 13:57 ` [PATCH 3/3] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-20 15:09 ` [PATCH v3 0/3] " David Marinović
2026-03-20 15:09 ` [PATCH v3 1/3] iio: dac: ltc2632: drop enum and use individual chip_info objects David Marinović
2026-03-20 15:09 ` [PATCH v3 2/3] dt-bindings: iio: dac: ltc2632: add LTC2654 compatible strings David Marinović
2026-03-20 17:20 ` Conor Dooley
2026-03-21 15:39 ` Jonathan Cameron
2026-03-20 15:09 ` [PATCH v3 3/3] iio: dac: ltc2632: add support for LTC2654 DAC family David Marinović
2026-03-21 15:38 ` Jonathan Cameron
2026-03-21 15:30 ` [PATCH v3 0/3] " Jonathan Cameron
2026-03-21 15:41 ` Jonathan Cameron
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=abq9RCfFjGVzhrMg@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=conor+dt@kernel.org \
--cc=david.marinovic@pupin.rs \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=robh@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