From: Javier Arteaga <javier@emutex.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
"Dan O'Donovan" <dan@emutex.com>,
Javier Arteaga <javier@emutex.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] iio: adc128s052: allow driver to be matched using ACPI
Date: Thu, 19 Apr 2018 14:20:35 +0100 [thread overview]
Message-ID: <20180419132036.27493-2-javier@emutex.com> (raw)
In-Reply-To: <20180419132036.27493-1-javier@emutex.com>
From: Dan O'Donovan <dan@emutex.com>
Allow driver to be matched by compatible string in
ACPI device properties.
Signed-off-by: Dan O'Donovan <dan@emutex.com>
---
drivers/iio/adc/ti-adc128s052.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/adc/ti-adc128s052.c b/drivers/iio/adc/ti-adc128s052.c
index 7cf39b3e2416..56ec04d1c68f 100644
--- a/drivers/iio/adc/ti-adc128s052.c
+++ b/drivers/iio/adc/ti-adc128s052.c
@@ -202,7 +202,7 @@ MODULE_DEVICE_TABLE(spi, adc128_id);
static struct spi_driver adc128_driver = {
.driver = {
.name = "adc128s052",
- .of_match_table = of_match_ptr(adc128_of_match),
+ .of_match_table = adc128_of_match,
},
.probe = adc128_probe,
.remove = adc128_remove,
--
2.17.0
next prev parent reply other threads:[~2018-04-19 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 13:20 [PATCH 0/2] ACPI match adc128s052 to ADC on UP Squared Javier Arteaga
2018-04-19 13:20 ` Javier Arteaga [this message]
2018-04-21 15:54 ` [PATCH 1/2] iio: adc128s052: allow driver to be matched using ACPI Jonathan Cameron
2018-04-21 20:41 ` Javier Arteaga
2018-04-24 17:23 ` Jonathan Cameron
2018-04-24 19:33 ` Javier Arteaga
2018-04-19 13:20 ` [PATCH 2/2] iio: adc128s052: add ACPI _HID AANT1280 Javier Arteaga
2018-04-21 16:05 ` Jonathan Cameron
2018-04-21 20:46 ` Javier Arteaga
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=20180419132036.27493-2-javier@emutex.com \
--to=javier@emutex.com \
--cc=dan@emutex.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.