From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Marius Cristea <marius.cristea@microchip.com>,
Trevor Gamblin <tgamblin@baylibre.com>,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>,
Hans de Goede <hdegoede@redhat.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v2 00/13] iio: Clean up acpi_match_device() use cases
Date: Thu, 24 Oct 2024 16:08:16 +0300 [thread overview]
Message-ID: <ZxpGwOcreTRCdEgR@smile.fi.intel.com> (raw)
In-Reply-To: <20241024130424.3818291-1-andriy.shevchenko@linux.intel.com>
On Thu, Oct 24, 2024 at 03:36:05PM +0300, Andy Shevchenko wrote:
> There are current uses of acpi_match_device():
> - as strange way of checking if the device was enumerated via ACPI
> - as a way to get IIO device name as ACPI device instance name
> - as above with accompanying driver data
>
> Deduplicate its use by providing two new helper functions in IIO ACPI
> library and update the rest accordingly.
>
> This also includes a rework of previously sent ltr501 patch.
> In v2:
> - collected tags (Hans, Jean-Baptiste)
> - updated SoB chain in patch 4
Heck, I forgot to address the main comment by Jonathan! Sorry for the noise,
I will send a v3 later today.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-10-24 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 12:36 [PATCH v2 00/13] iio: Clean up acpi_match_device() use cases Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 01/13] iio: magnetometer: bmc150: Drop dead code from the driver Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 02/13] iio: adc: pac1934: Replace strange way of checking type of enumeration Andy Shevchenko
2024-10-24 13:25 ` Marius.Cristea
2024-10-24 12:36 ` [PATCH v2 03/13] iio: imu: inv_mpu6050: " Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 04/13] iio: acpi: Improve iio_read_acpi_mount_matrix() Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 05/13] iio: acpi: Add iio_get_acpi_device_name_and_data() helper function Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 06/13] iio: accel: mma9551: Replace custom implementation of iio_get_acpi_device_name() Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 07/13] iio: accel: mma9553: " Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 08/13] iio: gyro: bmg160: " Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 09/13] iio: light: isl29018: Replace a variant of iio_get_acpi_device_name_and_data() Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 10/13] iio: light: isl29018: drop ACPI_PTR() and CONFIG_ACPI guards Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 11/13] iio: light: ltr501: Drop most likely fake ACPI IDs Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 12/13] iio: light: ltr501: Add LTER0303 to the supported devices Andy Shevchenko
2024-10-24 12:36 ` [PATCH v2 13/13] iio: light: ltr501: Replace a variant of iio_get_acpi_device_name_and_data() Andy Shevchenko
2024-10-24 13:08 ` Andy Shevchenko [this message]
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=ZxpGwOcreTRCdEgR@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=hdegoede@redhat.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=tgamblin@baylibre.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