All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
To: jikos@kernel.org, jic23@kernel.org, srinivas.pandruvada@linux.intel.com
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	sakari.ailus@linux.intel.com, sanjayembeddedse@gmail.com,
	linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 04/10] iio: pressure: adapt to hid_sensor_remove_trigger() API change
Date: Tue, 28 Apr 2026 12:46:07 +0530	[thread overview]
Message-ID: <20260428071613.1134053-5-sanjayembedded@gmail.com> (raw)
In-Reply-To: <20260428071613.1134053-1-sanjayembedded@gmail.com>

From: Sanjay Chitroda <sanjayembeddedse@gmail.com>

Update the driver to match the updated hid_sensor_remove_trigger()
prototype, which no longer requires struct iio_dev.

Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
---
 drivers/iio/pressure/hid-sensor-press.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/iio/pressure/hid-sensor-press.c b/drivers/iio/pressure/hid-sensor-press.c
index 5f1d6abda3e4..2bf5d055e175 100644
--- a/drivers/iio/pressure/hid-sensor-press.c
+++ b/drivers/iio/pressure/hid-sensor-press.c
@@ -319,7 +319,7 @@ static int hid_press_probe(struct platform_device *pdev)
 error_iio_unreg:
 	iio_device_unregister(indio_dev);
 error_remove_trigger:
-	hid_sensor_remove_trigger(indio_dev, &press_state->common_attributes);
+	hid_sensor_remove_trigger(&press_state->common_attributes);
 	return ret;
 }
 
@@ -332,7 +332,7 @@ static void hid_press_remove(struct platform_device *pdev)
 
 	sensor_hub_remove_callback(hsdev, HID_USAGE_SENSOR_PRESSURE);
 	iio_device_unregister(indio_dev);
-	hid_sensor_remove_trigger(indio_dev, &press_state->common_attributes);
+	hid_sensor_remove_trigger(&press_state->common_attributes);
 }
 
 static const struct platform_device_id hid_press_ids[] = {
-- 
2.34.1


  parent reply	other threads:[~2026-04-28  7:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  7:16 [PATCH 00/10] iio: drop redundant iio_dev argument from hid_sensor_remove_trigger() Sanjay Chitroda
2026-04-28  7:16 ` [PATCH 01/10] iio: hid-sensors: drop redundant iio_dev argument Sanjay Chitroda
2026-04-28  7:16 ` [PATCH 02/10] iio: orientation: adapt to hid_sensor_remove_trigger() API change Sanjay Chitroda
2026-04-28  8:22   ` Andy Shevchenko
2026-04-28 12:06     ` Sanjay Chitroda
     [not found]     ` <39108D2A-3C3F-40B5-9A9B-5B3572A63922@gmail.com>
2026-04-28 16:12       ` Jonathan Cameron
2026-04-28  7:16 ` [PATCH 03/10] iio: gyro: " Sanjay Chitroda
2026-04-28  7:16 ` Sanjay Chitroda [this message]
2026-04-28  7:16 ` [PATCH 05/10] iio: temperature: " Sanjay Chitroda
2026-04-28  7:16 ` [PATCH 06/10] iio: humidity: " Sanjay Chitroda
2026-04-28  7:16 ` [PATCH 07/10] iio: light: " Sanjay Chitroda
2026-04-28  7:16 ` [PATCH 08/10] iio: magnetometer: " Sanjay Chitroda
2026-04-28  7:16 ` [PATCH 09/10] iio: position: " Sanjay Chitroda
2026-04-28  7:16 ` [PATCH 10/10] iio: accel: " Sanjay Chitroda

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=20260428071613.1134053-5-sanjayembedded@gmail.com \
    --to=sanjayembeddedse@gmail.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=srinivas.pandruvada@linux.intel.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.