From: Dmitry Mastykin <mastichi@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Dmitry Mastykin <mastichi@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Rob Herring <robh@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2] iio: adc: max9611: fix module auto-loading
Date: Fri, 29 Dec 2017 16:59:48 +0300 [thread overview]
Message-ID: <1514556006-23293-1-git-send-email-mastichi@gmail.com> (raw)
The simplest fix is to move to ->probe_new() since the driver is not
used out of DT/ACPI enumeration.
Signed-off-by: Dmitry Mastykin <mastichi@gmail.com>
---
drivers/iio/adc/max9611.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/adc/max9611.c b/drivers/iio/adc/max9611.c
index b1dd17c..ce0115a 100644
--- a/drivers/iio/adc/max9611.c
+++ b/drivers/iio/adc/max9611.c
@@ -523,8 +523,7 @@ static const struct of_device_id max9611_of_table[] = {
};
MODULE_DEVICE_TABLE(of, max9611_of_table);
-static int max9611_probe(struct i2c_client *client,
- const struct i2c_device_id *id)
+static int max9611_probe(struct i2c_client *client)
{
const char * const shunt_res_prop = "shunt-resistor-micro-ohms";
const struct device_node *of_node = client->dev.of_node;
@@ -576,7 +575,7 @@ static struct i2c_driver max9611_driver = {
.owner = THIS_MODULE,
.of_match_table = max9611_of_table,
},
- .probe = max9611_probe,
+ .probe_new = max9611_probe,
};
module_i2c_driver(max9611_driver);
--
2.7.4
next reply other threads:[~2017-12-29 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 13:59 Dmitry Mastykin [this message]
2017-12-29 15:30 ` [PATCH v2] iio: adc: max9611: fix module auto-loading Andy Shevchenko
2017-12-29 17:54 ` Jonathan Cameron
2017-12-30 12:43 ` Dmitry Mastykin
2018-01-01 9:53 ` Jonathan Cameron
2018-01-03 12:41 ` Dmitry Mastykin
2018-01-06 13:14 ` Jonathan Cameron
2018-01-06 21:37 ` Dmitry Mastykin
2018-01-07 16:08 ` Jonathan Cameron
2018-01-09 11:07 ` Dmitry Mastykin
2018-01-10 3:51 ` Dmitry Mastykin
2018-01-10 11:03 ` Javier Martinez Canillas
2018-01-10 11:01 ` Javier Martinez Canillas
2018-01-14 10:51 ` Jonathan Cameron
2018-01-15 12:31 ` Javier Martinez Canillas
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=1514556006-23293-1-git-send-email-mastichi@gmail.com \
--to=mastichi@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=jacopo+renesas@jmondi.org \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).