Messages in this thread | | | From | Octavian Purdila <> | Subject | [PATCH v3 0/2] fix drivers that consider 0 as a valid IRQ in client->irq | Date | Fri, 5 Jun 2015 16:59:41 +0300 |
| |
Since patch "i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned" [1], 0 is not a valid i2c client irq anymore, so change all driver's checks accordingly.
The same issue occurs when the device is instantiated via device tree with no IRQ, or from the i2c sysfs interface, even before the patch above.
[1] http://lkml.kernel.org/g/<1430908148-201129-3-git-send-email-mika.westerberg@linux.intel.com>
Changes since v2:
* switch to using https://lkml.kernel.org/ instead of lkml.org
Changes since v1:
* remove the commit id as the referenced patch is not yet merged
* rephrased the subject line to be more descriptive
Octavian Purdila (2): iio: fix drivers that consider 0 as a valid IRQ in client->irq rtc: fix drivers that consider 0 as a valid IRQ in client->irq
drivers/iio/accel/bmc150-accel.c | 2 +- drivers/iio/accel/kxcjk-1013.c | 2 +- drivers/iio/accel/mma9553.c | 2 +- drivers/iio/imu/kmx61.c | 8 ++++---- drivers/rtc/rtc-ds1374.c | 4 ++-- drivers/rtc/rtc-ds3232.c | 2 +- 6 files changed, 10 insertions(+), 10 deletions(-)
-- 1.9.1
| |